Wireless power transfer network management

ABSTRACT

Concepts and technologies directed to wireless power transfer network management are disclosed herein. Embodiments of a system can include an optical beamforming transmitter, a processor, and a memory that stores computer-executable instructions that configure a processor to perform operations. The operations can include receiving a power charge message that requests wireless power transfer to charge a battery system of a wirelessly chargeable equipment. The operations can include detecting that the wirelessly chargeable equipment is within a power transfer range of the optical beamforming transmitter. The operations can include determining that the wirelessly chargeable equipment is not stationary. The operations can include tracking movement of the wirelessly chargeable equipment and activating the optical beamforming transmitter that provides wireless power transfer to the wirelessly chargeable equipment while the wirelessly chargeable equipment is within the power transfer range.

BACKGROUND

Historically, vehicles have operated using combustion as a primary powersource to drive movement. In recent years, an increasing number ofvehicles and user equipment utilize electric motors to drive movement.As such, many vehicles and other user equipment incorporate batterysystems that store an electric charge for later use. Yet the amount ofpower which can be stored by battery systems is finite, and thus when avehicle or other user equipment draws from the battery system store, thepower is depleted. Electric vehicles and devices (e.g., full electricvehicles, hybrid vehicles, electric scooters, mobile devices, etc.) mayhave limited operating distance and/or time depending on the manner inwhich each device is used. Although infrastructure for replenishingelectric vehicles and devices is increasing, there still exists thepossibility that a user becomes stranded between designated electricre-charging stations or hubs. Extended periods away from a power sourcecan, in some instances, cause an electric vehicle and/or device to loseelectric charge, such as through electrical parasitic loss.Additionally, users who rely on a vehicle's battery system to rechargeuser equipment (e.g., a mobile phone, tablet, smart device, etc.) canincrease the power draw from the battery system, and in turn deplete thecurrent electric charge.

SUMMARY

The present disclosure is directed to wireless power transfer networkmanagement, according to various embodiments. According to one aspect ofthe concepts and technologies disclosed herein, a system is disclosed.In some embodiments, the system can include or otherwise be provided bya network server, a network edge device, a wireless power transferassembly, a network access point, a combination thereof, or the like.The system can be communicatively coupled to a network. In someembodiments, the system can include an optical beamforming transmitter,a processor, and a memory. The memory can store computer-executableinstructions that, in response to execution by the processor, cause theprocessor to perform operations. In some embodiments, the operations caninclude receiving a power charge message. The power charge message canrequest wireless power transfer to charge a battery system of awirelessly chargeable equipment. In some embodiments, the power chargemessage can include a wirelessly chargeable equipment identifier and alocation identifier. The operations can further include detecting thatthe wirelessly chargeable equipment is within a power transfer range ofthe optical beamforming transmitter. In some embodiments, the operationscan include determining that the wirelessly chargeable equipment is notstationary. In some embodiments, the operations can include trackingmovement of the wirelessly chargeable equipment. In some embodiments,the operations can further include obtaining a current charge profilecorresponding to the wirelessly chargeable equipment, where the currentcharge profile can include a charge criticality indicator and a currentcharge level.

In some embodiments, the operations can include determining whether thewirelessly chargeable equipment is authorized to receive the wirelesspower transfer. In some embodiments, the operations can includeactivating the optical beamforming transmitter that provides wirelesspower transfer to the wirelessly chargeable equipment while thewirelessly chargeable equipment is within the power transfer range. Insome embodiments, activating the optical beamforming transmitter canoccur after determining that the wirelessly chargeable equipment isauthorized to receive the wireless power transfer.

In some embodiments, the operations can include generating, prior to thewirelessly chargeable equipment leaving the power transfer range, acharge preparation command that is directed to a downstream wirelesspower transfer assembly that is located outside of the power transferrange. In some embodiments, the downstream wireless power transferassembly can include another optical beamforming transmitter to provideanother instance of wireless power transfer once the wirelesslychargeable equipment leaves the power transfer range. In someembodiments, the operations can include providing the charge preparationcommand to the downstream wireless power transfer assembly that islocated outside of the power transfer range. In various embodiments, thecharge preparation command can instruct the downstream wireless powertransfer assembly to prepare to provide wireless power transfer for thewirelessly chargeable equipment. In some embodiments, the operations caninclude confirming a direct line of sight with the wirelessly chargeableequipment. In some embodiments, the optical beamforming transmitter canbe activated responsive to confirming a direct line of sight with thewirelessly chargeable equipment.

According to another aspect of the concepts and technologies disclosedherein, a method is disclosed according to an embodiment. In variousembodiments, the method may be performed by a system that includes anoptical beamforming transmitter. In some embodiments, the system can beconfigured as a network edge device, where the optical beamformingtransmitter is provided by a wireless power transfer assembly of thenetwork edge device. In some embodiments, the network edge device canalso include a network access point. In various embodiments, the methodcan include receiving, by a system that provides an optical beamformingtransmitter, a power charge message. The power charge message canrequest wireless power transfer to charge a battery system of awirelessly chargeable equipment. In some embodiments, the power chargemessage can include a wirelessly chargeable equipment identifier and alocation identifier. The method can further include detecting, by thesystem, that the wirelessly chargeable equipment is within a powertransfer range of the optical beamforming transmitter. In someembodiments, the method can include determining, by the system, that thewirelessly chargeable equipment is not stationary. In some embodiments,the method can include tracking, by the system, movement of thewirelessly chargeable equipment. In some embodiments, the method canfurther include obtaining, by the system, a current charge profilecorresponding to the wirelessly chargeable equipment, where the currentcharge profile can include a charge criticality indicator and a currentcharge level.

In some embodiments, the method can include determining, by the system,whether the wirelessly chargeable equipment is authorized to receive thewireless power transfer. In some embodiments, the method can includeactivating, by the system, the optical beamforming transmitter thatprovides wireless power transfer to the wirelessly chargeable equipmentwhile the wirelessly chargeable equipment is within the power transferrange. In some embodiments, activating the optical beamformingtransmitter can occur after determining that the wirelessly chargeableequipment is authorized to receive the wireless power transfer.

In some embodiments, the method can include generating, by the system,prior to the wirelessly chargeable equipment leaving the power transferrange, a charge preparation command that is directed to a downstreamwireless power transfer assembly that is located outside of the powertransfer range. In some embodiments, the downstream wireless powertransfer assembly can include another optical beamforming transmitter toprovide wireless power transfer once the wirelessly chargeable equipmentleaves the power transfer range. In some embodiments, the method caninclude providing the charge preparation command to the downstreamwireless power transfer assembly that is located outside of the powertransfer range. In various embodiments, the charge preparation commandcan instruct the downstream wireless power transfer assembly to prepareto provide wireless power transfer for the wirelessly chargeableequipment. In some embodiments, the method can include confirming, bythe system, a direct line of sight with the wirelessly chargeableequipment. In some embodiments, the optical beamforming transmitter canbe activated responsive to confirming a direct line of sight with thewirelessly chargeable equipment.

According to another aspect of the concepts and technologies disclosedherein, a computer storage medium is disclosed according to anembodiment. The computer storage medium can have computer-executableinstructions stored thereon that, in response to execution by aprocessor of a system, cause the processor to perform operations. Insome embodiments, the system can include an optical beamformingtransmitter. The operations can include receiving a power chargemessage. The power charge message can request wireless power transfer tocharge a battery system of a wirelessly chargeable equipment. In someembodiments, the power charge message can include a wirelesslychargeable equipment identifier and a location identifier. Theoperations can further include detecting that the wirelessly chargeableequipment is within a power transfer range of the optical beamformingtransmitter. In some embodiments, the operations can include determiningthat the wirelessly chargeable equipment is not stationary. In someembodiments, the operations can include tracking movement of thewirelessly chargeable equipment. In some embodiments, the operations canfurther include obtaining a current charge profile corresponding to thewirelessly chargeable equipment, where the current charge profile caninclude a charge criticality indicator and a current charge level.

In some embodiments, the operations can include determining whether thewirelessly chargeable equipment is authorized to receive the wirelesspower transfer. In some embodiments, the operations can includeactivating the optical beamforming transmitter that provides wirelesspower transfer to the wirelessly chargeable equipment while thewirelessly chargeable equipment is within the power transfer range. Insome embodiments, activating the optical beamforming transmitter canoccur after determining that the wirelessly chargeable equipment isauthorized to receive the wireless power transfer.

In some embodiments, the operations can include generating, prior to thewirelessly chargeable equipment leaving the power transfer range, acharge preparation command that is directed to a downstream wirelesspower transfer assembly that is located outside of the power transferrange. In some embodiments, the downstream wireless power transferassembly can include another optical beamforming transmitter to providewireless power transfer once the wirelessly chargeable equipment leavesthe power transfer range. In some embodiments, the operations caninclude providing the charge preparation command to the downstreamwireless power transfer assembly that is located outside of the powertransfer range. In various embodiments, the charge preparation commandcan instruct the downstream wireless power transfer assembly to prepareto provide wireless power transfer for the wirelessly chargeableequipment. In some embodiments, the operations can include confirming adirect line of sight with the wirelessly chargeable equipment. In someembodiments, the optical beamforming transmitter can be activatedresponsive to confirming the direct line of sight with the wirelesslychargeable equipment.

It should be appreciated that the above-described subject matter may beimplemented as a computer-controlled apparatus, a computer process, acomputing system, a method, or as an article of manufacture such as acomputer storage medium. These and various other features will beapparent from a reading of the following Detailed Description and areview of the associated drawings.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intendedthat this Summary be used to limit the scope of the claimed subjectmatter. Furthermore, the claimed subject matter is not limited toimplementations that solve any or all disadvantages noted in any part ofthis disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example operating environmentfor implementing wireless power transfer network management, accordingto an illustrative embodiment.

FIG. 2 is a block diagram illustrating aspects of a vehicle capable ofimplementing aspects of the embodiments disclosed herein.

FIG. 3 is a flow diagram illustrating aspects of a method for wirelesspower transfer network management, according to an illustrativeembodiment.

FIG. 4 is a flow diagram illustrating aspects of another method forfacilitating wireless power transfer network management, according to anillustrative embodiment.

FIG. 5 is a diagram illustrating an example network capable ofimplementing aspects of the embodiments discussed herein.

FIG. 6 is a block diagram illustrating an example computer systemcapable of implementing aspects of the embodiments presented anddescribed herein.

FIG. 7 is a diagram illustrating an example user equipment capable ofimplementing aspects of the concepts and technologies described hereinaccording to embodiments of the present disclosure.

DETAILED DESCRIPTION

The following detailed description is directed to wireless powertransfer network management that facilitates direct, individualizedwireless power transfer to rechargeable equipment that is non-stationaryand/or stationary, according to various embodiments. Traditionalattempts at providing power transfer to electric vehicles and/or otherrechargeable equipment typically require a vehicle and/or device to bestationary and physically attached to a power cable for an extendedperiod of time. As such, the physical coupling of a power cable forpower delivery can limit the mobility of the user depending on thelength of the power cable. When a user is at home and/or at work forextended periods of time, the electric vehicle and/or device may bestationary, and thus restrictions regarding the mobility of the electricvehicle and/or device may not bother the user. In addition to physicalpower cables limiting physical movement, the power cables themselves canexhibit wear over time due to repeated use. Moreover, the physicaldesign of a connector interface for the power cable may need to bedesigned for uniformity across various manufacturers, therebycomplicating the design process and increasing costs.

Some traditional attempts at wireless power transfer, that is powertransfer without relying on attachment to a physical cable, have usedelectromagnetic induction in near-field and/or far-field scenarios. Forexample, some attempts at providing wireless power transfer to anelectric vehicle require that the vehicle be parked over an inductionpower transmitter that is embedded or otherwise buried in the ground.Other traditional attempts may provide an induction power transmitterlocated on the ceiling of a room such that when a user brings theirmobile device into the room, the mobile device is charged via theelectromagnetic field produced by the induction transmitter. Yet use ofan induction transmitter for wireless power transfer can providesignificant technical challenges because all wirelessly chargeabledevices that are located within the electromagnetic field of theinduction transmitter will have an opportunity to receive wireless powertransfer. This is because wireless power transfer systems which use aninduction transmitter typically cannot distinguish target devices fromother devices and provide isolated wireless power transfer to aparticular device when multiple devices are located next to each other.Therefore, wireless power transfer systems that utilize an inductiontransmitter may inadvertently provide power transfer to devices and/orvehicles that are not authorized by a service provider to receive thepower transfer because these devices are located within theelectromagnetic field. Therefore, managing and providing wireless powertransfer in large scale operations by relying solely on electromagneticinduction may present significant technical challenges when conventionaltechniques and conventional systems are utilized.

As such, embodiments of the present disclosure provide concepts andtechnology for wireless power transfer network management thatfacilitates direct, individualized wireless power transfer torechargeable equipment that is non-stationary and/or stationary. Theconcepts and technologies discussed herein can enable wirelesslychargeable equipment (e.g., an electric vehicle, a remote controlleddevice, a mobile phone that is in motion, or another user equipment thatis configured for wireless power transfer) to receive wireless powertransfer via the use of an optical beamforming transmitter. Embodimentsof the present disclosure can provide components which enable devicerecognition and movement tracking so that wireless power transfer can beprovided by the optical beamforming transmitter while the wirelesslychargeable equipment is within a power transfer range. The concepts andtechnologies discussed herein can provide a plurality of network edgedevices that include an optical beamforming transmitter and areconfigured to communicate with each other to facilitate continuous,selective wireless power transfer to the wirelessly chargeable equipmentas the wirelessly chargeable equipment moves between the network edgedevices. The network edge devices can collectively form a wireless powertransfer network that enables far field wireless power transfer tospecific wirelessly chargeable equipment. In some embodiments, a networkedge device can serve as a wireless power transfer node via an opticalbeamforming transmitter, and also serve as a network communicationaccess point for a mobile network, such as by including components of abase transceiver station, an eNodeB, a gNodeB, or other networkcommunication node. By this, a communication service provider canidentify and selectively authorize wirelessly chargeable equipment toreceive wireless power transfer without sole reliance on an inductiontransmitter. Therefore, various concepts and technologies of embodimentsdiscussed herein can improve the functioning of wirelessly chargeableequipment by providing increased operating range through selectivewireless power transfer, while also mitigating waste of electricalresources by authorizing wireless power transfer to specific wirelesslychargeable equipment. These and other aspects of the concepts andtechnologies disclosed herein will be illustrated and described in moredetail below.

While some of the subject matter described herein may occasionally bepresented in the general context of program modules that execute inconjunction with the execution of an operating system and applicationprograms on a computer system, those skilled in the art will recognizethat other implementations may be performed in combination with othertypes of program modules. Generally, program modules include routines,programs, components, data structures, and other types of structuresthat perform particular tasks or implement particular abstract datatypes in response to execution on a processor so as to transform theprocessor into a particular machine. Moreover, those skilled in the artwill appreciate that the subject matter described herein may bepracticed with other computer system configurations, including hand-helddevices, vehicle computer systems, network access nodes, networkservers, multiprocessor systems, microprocessor-based or programmableconsumer electronics, minicomputers, mainframe computers, and otherparticularized, non-generic machines.

Referring now to FIG. 1, aspects of an operating environment 100 forimplementing various embodiments of the concepts and technologiesdisclosed herein pertaining to a network edge device that provides orotherwise facilitates network management for wireless power transferwill be described, according to an illustrative embodiment. It should beunderstood that the operating environment 100 and the various componentsthereof have been illustrated for clarity purposes to simplify themanner of discussion. Accordingly, additional and/or alternatecomponents can be made available or otherwise implemented within theoperating environment 100 without departing from the embodimentsdescribed herein. As such, the manner of discussion is provided suchthat one of ordinary skill in the technology can implement one or moreembodiments described herein.

The operating environment 100 shown in FIG. 1 includes a plurality ofwirelessly chargeable devices (“WCEs”), such as a WCE 102 and a WCE 118,a plurality of network edge devices (“NED”), such as NEDs 140, 160, and164, a communications network (“network”) 120, a network server 122, apower grid 130, and one or more instance of a radio access network(“RAN”) 132. The number of instances shown in FIG. 1 is for illustrationpurposes only and should not be construed as limiting in any way.Therefore, it is understood that zero, one, two, or more instances ofeach of the components shown in FIG. 1 may be provided in variousembodiments.

In the operating environment 100 shown in FIG. 1, the plurality of WCEs(e.g., the WCE 102, 118) are illustrated as being configured asrechargeable electric vehicles driving along a paved roadway, althoughthis may not necessarily be the case for all embodiments. As usedherein, the term “wirelessly chargeable equipment” (e.g., any of theWCEs 102, 118) refers to any device and/or machine that has arechargeable battery unit (e.g., a battery system with rechargeablebattery cells as discussed below in further detail) and is configured toreceive wireless power transfer from an optical beamforming transmittersuch that the optical beamforming transmitter provides or otherwisefacilitates energy transfer to recharge the battery system of thewirelessly chargeable equipment. More specifically, various embodimentsof the wirelessly chargeable equipment are configured to receiveon-demand, targeted, laser-based wireless power transfer without use ofinductive power transfer (i.e., without use of electromagnetic fieldsprovided by inductive coupling) and/or without radio frequency wirelesspower transfer (i.e., without reliance on radio signals between threekilohertz to three-hundred gigahertz frequency to transfer power). Assuch, various embodiments of the present disclosure can provide a systemthat can provide an access point for data communication and also canprovide laser-based wireless power transfer. Unlike traditional systemswhich rely on inductive wireless power transfer and/or radio frequencywireless power transfer, embodiments of the present disclosure canprovide laser-based wireless power transfer that can reduce potentialspectrum interferences in data transmission during power transfer, andalso limit contribution to electromagnetic pollution in the particularoperating environment. By this, aspects and embodiments of the presentdisclosure can improve the field of network communication and wirelesspower transfer by enabling network edge devices to serve as a node forlaser-based wireless power transfer without interfering with wirelessnetwork communications, thereby allowing a network access point to beco-located with components that provide the laser-based wireless powertransfer, such as further discussed below.

In various embodiments, an instance of a wirelessly chargeable equipment(e.g., any of the WCE 102, 118) can be configured as a ground-basedvehicle (a car, a truck, a van, a sport utility vehicle, a cross-overvehicle, a motorcycle, a motorized tricycle, a scooter, a go-kart, agolf cart, a fork lift, a bus, a semi-trailer truck, a racing vehicle, asnow-capable vehicle, earth-moving equipment, farming/agricultureequipment, combinations thereof, or any other vehicle that is configuredto receive laser-based wireless power transfer), an air-based vehicle(e.g., an unmanned aircraft vehicle, a remote-controlled vehicle, and/orany other flying vehicle that is configured to receive laser-basedwireless power transfer), a user equipment (e.g., a smart phone, atablet, a head unit within a vehicle, an Internet of Things device,and/or any other user equipment that is configured to receivelaser-based wireless power transfer for energy replenishment), and/orany other device that is configured to receive laser-based wirelesspower transfer for energy replenishment. Although two instances of a WCE(e.g., the WCE 102, 118) are illustrated in FIG. 1, it is understoodthat less than two or more than two instances of a WCE can be includedin the operating environment 100. It should be understood that theexamples provided are for illustration purposes only, and thereforeshould not be construed as limiting in any way.

In some embodiments, the WCE 102 and the WCE 118 can be configuredsubstantially similar to each other. For clarity purposes, a discussionof the WCE 102 will be provided. It is understood that any elements ofthe WCE 102 can be included in the WCE 118. Furthermore, in someembodiments, one or more aspects of a vehicle may be included in any ofthe WCE 102 and/or the WCE 118, such as discussed below with respect toFIG. 2. Therefore, it should be understood that the examples providedare for illustration purposes only, and therefore should not beconstrued as limiting in any way.

As shown in FIG. 1, the WCE 102 can include a head unit 103. The headunit 103 can include one or more instances of a processor, memory,circuitry, and/or a display for presenting a user interface that canprovide visual images and/or audiovisual input and output. The head unit103 also can include (and/or be communicatively coupled to) input andoutput components that provide audio output and receive input from auser, such as via one or more speakers and/or microphones. In someembodiments, the head unit 103 can be configured to include a heads updisplay, a vehicle information display, a console display, blind spotalert mechanisms, a combination thereof, or any other audio, visual,and/or haptic feedback mechanism that can communicate or conveyinformation to a user associated with the WCE 102. In some embodiments,information and data pertaining to wireless power transfer can beprovided or otherwise presented to a user via the head unit 103 throughvisual presentation and/or audio presentation. It should be understoodthat the examples provided are for illustration purposes only, andtherefore should not be construed as limiting in any way.

In various embodiments, the WCE 102 can include a telematics controlunit (“TCU”) 104. In various embodiments, the TCU 104 can be configuredsubstantially similar to a TCU discussed with respect to FIG. 2. The TCU104 can include communication components and circuitry that provide andsupport communicative coupling with other devices and networks, such asbut not limited to, the network 120, the network server 122, the RAN132, the NED 140, the NED 160, and/or the NED 164. The TCU 104 can send,receive, and/or control communication flow to/from the head unit 103. Invarious embodiments, the TCU 104 can provide an embedded computingsystem for vehicle tracking and location information. As such, invarious embodiments, the TCU 104 can include one or more of a globalposition system unit, an external interface for mobile communication(e.g., GSM, GPRS, Wi-Fi, WiMax, 3G, 4G, LTE, 5G New Radio (“NR”), etc.)to provide communicative coupling, a processor, a memory, and othercomponents to enable or otherwise facilitate equipment tracking andcommunication. In some embodiments, the TCU 104 can indicate an amountof signal strength, available network connections, and other informationpertaining to communication to/from and/or location of the WCE 102. Insome embodiments, information provided by the TCU 104 can be presentedto a user via the head unit 103. The TCU 104 can expose one or morenetwork communication interfaces that provide communication links to anetwork access point, such as a network access point 152 provided by theNED 140, as discussed below in further detail.

In various embodiments, each instance of a WCE can correspond with a WCEidentifier, such as the WCE 102 corresponding with a WCE identifier 108.An instance of the WCE identifier 108 can be unique to the particularWCE that is configured to receive laser-based wireless power transfer.As such, an instance of the WCE identifier 108 can be used by networkinfrastructure to determine whether the WCE 102 is authorized to accessand utilize a wireless power transfer service (“WPT service”) 124.Further discussion of the WPT service 124 is provided below. In someembodiments, the WCE identifier 108 may include and/or correspond withan international mobile equipment identity, a subscriber identity modulenumber, an electronic serial number, a combination thereof, or anotheridentifier assigned or associated with the WCE 102. It is understoodthat the examples provided are for illustration purposes only, andtherefore should not be construed as limiting in any way.

In various embodiments, an instance of the TCU 104 can generate, store,and/or provide location information as to the current and/or formerlocation of the corresponding WCE (e.g., the WCE 102). In someembodiments, the TCU 104 can generate one or more instance of a locationidentifier 109 that can indicate the location of the WCE 102 at a givenpoint in time. For example, in some embodiments, the location identifier109 can provide GPS-based and/or non-GPS based location information,such as geo-coordinates, street addresses, cross-street identifiers,roadway or other thoroughfare markers, waypoint markers, network accesspoint identifiers, or any other data or information that can be used toindicate a geographic location of the WCE 102. In some embodiments, eachinstance of the location identifier 109 can provide a time marker thatindicates the point in time at which the location of the WCE 102 wasdetermined. In some embodiments, the TCU 104 can maintain a location logthat includes an instance of the location identifier 109, where the mostrecent instance in time of the location identifier 109 can be used as a“current” location for the WCE 102, even if the WCE 102 has moved awayor otherwise is no longer at the location corresponding to theparticular location identifier 109. In some embodiments, the TCU 104 canreport or otherwise provide instances of the location identifier 109 tothe NED 140 so as to facilitate tracking of the movement of the WCE 102.In some embodiments, the location identifier 109 may provide datapertaining to a direction 113 and a speed that the WCE 102 is travelingto yield a velocity 114 of the WCE 102. Through various instances of thelocation identifier 109, the NED 140 can prepare for when the WCE 102will be within a power transfer range for laser-based wireless powertransfer, such as a power transfer range 149 corresponding to the NED140 discussed below.

In various embodiments, an instance of the WCE 102 can include arechargeable battery system (“battery system”) 105. The battery system105 can be configured to provide a rechargeable power source tofacilitate various operations and energy consumption by a WCE (e.g., theWCE 102). The battery system 105 can include one or more instances of arechargeable battery cell 106 that is configured to provide powerstorage for one WCE (e.g., the WCE 102). The rechargeable battery cell106 can be manufactured through a variety of materials, such asnickel-metal hydride, lithium-ion, or other materials. Various instancesof the rechargeable battery cell 106 are understood by one of ordinaryskill in the technology, and therefore further discussion will not beprovided. The battery system 105 can indicate a current charge level 107corresponding to an amount of power remaining in the rechargeablebattery cell 106. In various embodiments, the current charge level 107can indicate the collective amount of current charge across allinstances of the rechargeable battery cell 106 that are included in thebattery system 105. In some embodiments, the current charge level 107may be measured in units of milli-amp hours (mAh), although this may notnecessarily be the case in all embodiments. In various embodiments, thecurrent charge level 107 can be indicated, presented, and/or provided toa device and/or display, such as to the head unit 103, the NED 140, thenetwork server 122, or the like. It is understood that the examplesprovided are for illustration purposes only, and therefore should not beconstrued as limiting in any way.

In some embodiments, a WCE (e.g., the WCE 102) can provide a chargecriticality indicator, such as a charge criticality indicator 110. Thecharge criticality indicator 110 can affect the adjustment and/orconfiguration of an optical beamforming transmitter that supportswireless power transfer, such as an optical beamforming transmitter(“OBFT”) 142 of the NED 140. A detailed discussion of the OBFT 142 willbe provided below. The charge criticality indicator 110 can represent anindication as to the urgency, criticality, and/or need for powertransfer to the WCE (e.g., the WCE 102). For example, in someembodiments, the charge criticality indicator 110 can be configured toindicate a “normal” criticality, a “low” criticality, and/or a “high”criticality. The “normal” criticality can indicate that the WCE 102requests wireless power transfer according to whatever default settingand/or standard configurations of the wireless power transfer source,such as a standard configurations of the OBFT 142 of the NED 140. Forexample, in some embodiments, if the OBFT 142 of the NED 140 isconfigured in a default setting to provide laser-based wireless powertransfer in a discontinuous beam (i.e., wireless power transferoccurring in laser bursts or pulses instead of a continuous laser beam),then the “normal” criticality indicated by the charge criticalityindicator 110 may trigger (or otherwise command) the NED 140 to maintainthe default setting of discontinuous wireless power transfer. As such,the NED 140 would not adjust the OBFT 142 to deviate from the defaultlaser configuration. In some embodiments, the “low” criticality canindicate that wireless power transfer is not urgent, and thus the NED140 can configure or otherwise adjust the OBFT 142 to reduce the amountof laser-based wireless power transfer to the WCE 102. For example, insome embodiments, the OBFT 142 can be adjusted to increase a time periodin between pulses in which a laser beam provides the wireless power. Forinstance, if the default setting provides laser pulses with a 15millisecond time period between each pulse, then the “normal”criticality would maintain the 15 millisecond time period fordiscontinuous wireless power transfer. If the “low” criticality isindicated by the charge criticality indicator 110, then the OBFT 142 canbe adjusted so that the time interval is increased (e.g., to a 200millisecond time period), thereby decreasing the overall amount ofwireless power transfer provided.

In some embodiments, the charge criticality indicator 110 can indicate a“high” criticality, which can command the NED 140 to provide additionalpower transfer above the default setting. In some embodiments, thecharge criticality indicator 110 can be set to the “high” criticalitywhen the WCE 102 is performing (or going to perform or otherwise engagein) operations that are sensitive to charge interruption, such asbecause the operations increase power demand on the WCE 102. Forexample, if a user is going to be engaging in an important phone call,or any other operation that may cause the WCE 102 to utilize anabove-average power draw from the battery system 105, then the WCE 102may become sensitive to charge interruptions because the rate at whichthe current charge level 107 will diminish is increased relative tonormal operations. As such, the WCE 102 can configure the chargecriticality indicator 110 to reflect the “high” criticality. In turn,the NED 140 and/or the network server 122 can be triggered to adjust theOBFT 142 in a manner that may provide additional laser-based wirelesspower transfer so as to offset the increased power draw on the WCE 102.For example, in some embodiments, when the charge criticality indicator110 represents or otherwise indicates that the WCE 102 is sensitive tocharge interruptions (e.g., due to high demand for power on the WCE102), then the NED 140 can be instructed to adjust the OBFT 142 so as todecrease, or in some embodiments eliminate, the time period betweenpulses or bursts of wireless power transfer, thereby increasing theoverall laser-based wireless power transfer provided (i.e., increasingthe overall amount of power transfer measured in mAh). As such, in someembodiments, the charge criticality indicator 110 can cause the NED 140to configure the OBFT 142 so as to provide a continuous laser beam, andthus continuous wireless power transfer to the WCE 102 instead of thedefault configuration, where the default may provide discontinuouswireless power transfer. The example discussed herein refers to thecharge criticality indicator 110 as providing three settings (e.g., low,normal, high), however this may not necessarily be the case in everyembodiment. In some embodiments, the charge criticality indicator 110may be configured as a flag such that, when provided to the NED 140, thepresence of the charge criticality indicator 110 can cause the OBFT 142to be reconfigured so as to provide additional power transfer, such asdiscussed with respect to the “high” criticality setting above.Therefore, the examples provided are for illustration purposes only, andshould not be construed as limiting in any way.

In various embodiments, a WCE (e.g., the WCE 102) can include a laserphotodetector that is configured to receive laser-based wireless powertransfer, such as from a laser beam 143 provided by the OBFT 142. Insome embodiments, an instance of a laser photodetector can include oneor more of an adjustable laser photodetector 111 and/or a fixedphotodetector 112. An instance of the adjustable laser photodetector 111can include a rotatable base 111A, a physical adjustment unit 111B, anda photovoltaic solar panel cell (“PSPC”) 111C. The rotatable base 111Acan mount or otherwise be attached to an exterior portion of a WCE(e.g., the WCE 102). The rotatable base 111A can provide a mountingsurface on which to mount the PSPC 111C. The rotatable base 111A can beconfigured to rotate the PSPC 111C in a clock-wise and/or counterclock-wise rotation, where the angle of rotation may be up to 360degrees. In some embodiments, the adjustable laser photodetector 111does not rotate 360 degrees continuously while in use. Instead, theadjustable laser photodetector 111 can be configured or otherwiseinstructed to maintain line-of-sight with an instance of the OBFT 142,which can increase energy transfer by placing more surface area of thePSPC 111C within the coverage of the laser beam 143 for power transfer.The physical adjustment unit 111B can include a motor, hydraulics,pistons, gears, belts, circuitry, and/or other components that canadjust or otherwise change a physical direction, rotation angle (e.g.,between 0-360 degrees clockwise and/or counter clockwise), and/orvertical angle (e.g., tilt angle measured 0-90 degrees) of the rotatablebase 111A and/or the PSPC 111C. As such, the physical adjustment unit111B can adjust the tilt of the PSPC 111C relative to the rotatable base111A and/or can adjust the rotatable base 111A between 0-360 degreesclockwise and/or counter clockwise as needed and/or instructed. Forexample, the PSPC 111C may, by default, be pointed in the same directionas the direction 113 the WCE 102 is traveling, and thus the defaultrotation angle would be considered to be zero degrees.

In this example, the PSPC 111C may have a vertical angle (e.g., tiltangle) that is zero degrees because the PSPC 111C may be substantiallyparallel to the rotatable base 111A and/or another mounting surface ofthe WCE 102. As such, in a default setting, the PSPC 111C may lay flatrelative to the WCE 102. In this example, the WCE 102 may receive anadjustment instruction from an NED, such as adjustment instruction 174that may be sent from the NED 140. The adjustment instruction 174 canprovide geographical location information of the corresponding NED thatwill be providing the laser-based wireless power transfer, such as a NEDlocation identifier 129A that can indicate location information aboutthe NED 140 which is and/or will be providing laser-based wireless powertransfer to the WCE 102. The adjustment instruction 174 can command thephysical adjustment unit 111B to configure the adjustable laserphotodetector 111 so as to maintain line of sight between the WCE 102and the NED (e.g., the NED 140) that is or will provide the wirelesspower transfer. For example, the physical adjustment unit 111B can beinstructed by the adjustment instruction 174 to adjust the rotatablebase 111A such that the PSPC 111C is constantly pointed towards the NED140. Therefore, when the WCE 102 is stationary, the physical adjustmentunit 111B may make a single adjustment of the rotational angle of therotatable base 111A so that the PSPC 111C is pointed towards the NED140.

Yet in some embodiments, the WCE 102 may be moving through a powertransfer range of a corresponding NED, such as one of power transferranges 149, 161, 165 corresponding to the NEDs 140, 160, and 164,respectively. A power transfer range (e.g., any of the power transferranges 149, 161, 165) refers to the geographical coverage area in whichlaser-based wireless power transfer can be provided by a correspondingNED (e.g., the NEDs 140, 160, and/or 164). Therefore, in someembodiments, as the WCE 102 moves through a power transfer range (e.g.,the power transfer range 149), the adjustable laser photodetector 111can maintain line of sight between the PSPC 111C and the OBFT 142 of theNED 140. Specifically, the physical adjustment unit 111B can providemultiple adjustments to the rotational angle of the rotatable base 111Aso that the PSPC 111C is continuously pointed towards the OBFT 142,thereby maintaining line of sight for wireless power transfer. In someembodiments, the vertical angle of the PSPC 111C may also be adjusted sothat the PSPC 111C is tilted vertically (e.g., between 1-90 degrees),thereby enabling a larger contact area for absorption of the laser beam143. In some embodiments, the physical adjustment unit 111B maycontinually (and/or intermittently) adjust the vertical angle of thePSPC 111C based on how far away the WCE 102 is from the correspondingNED (e.g., the NED 140) and based on the direction 113 that the WCE 102is moving relative to the NED 140.

In various embodiments, an instance of the PSPC 111C can includephotovoltaic materials that are configured in one or more layers. Thephotovoltaic materials can be configured to provide a semiconductor,where each layer is doped to absorb photons from the laser beam 143 aparticular wavelength spectrum, and in turn can create an electriccurrent that can be used to power the WCE 102. In various embodiments, aphotovoltaic material of the PSPC 111C can include, but should not belimited to, indium, gallium, nitrogen, graphene, silicone, combinationsthereof, or the like. In some embodiments, the laser beam 143 can beconfigured to provide and correspond with one or more wavelengths forultraviolet light (e.g., 10-380 nanometer wavelength), visible light(e.g., violet light from 380-450 nanometers, blue light from 450-495nanometers, green light from 495-570 nanometers, yellow light from570-590 nanometers, orange light from 590-620 nanometers, and red lightfrom 620-750 nanometers), or infrared light (e.g., 750-1,000,000nanometer wavelength). In various embodiments, the PSPC 111C can beconfigured so as to absorb photons from the laser beam 143.

In various embodiments, an instance of a WCE (e.g., the WCE 102) caninclude the fixed photodetector 112. The fixed photodetector 112 caninclude an instance of the PSPC 111C that is rigidly fixed or otherwiseattached to the WCE 102. As such, the fixed photodetector 112 may be ina fixed configuration relative to the WCE 102. In various embodiments,the fixed photodetector 112 can receive or otherwise obtain laser-basedwireless power transfer from a NED (e.g., the NED 140). In someembodiments, the WCE 102 may have one or more instances of the fixedphotodetector 112 that are placed at different portions of the WCE 102.For example, in an embodiment where the WCE 102 is configured as anelectric vehicle, instances of the fixed photodetector 112 may belocated on a roof, hood, trunk, headlight casing, door frames, or anyother part of the WCE 102. It is understood that the examples providedare for illustration purposes only, and therefore should not beconstrued as limiting in any way.

In various embodiments, an instance of a WCE (e.g., the WCE 102) canprovide or otherwise send a power charge message, such as a power chargemessage 170, to one or more of a NED (e.g., the NED 140), the RAN 132,the network 120, and/or the network server 122. The power charge message170 can request wireless power transfer to charge the battery system 105of the WCE 102. In some embodiments, the power charge message 170 caninclude an instance of the WCE identifier 108 and one or more instancesof the location identifier 109. In some embodiments, the power chargemessage 170 can be generated by an instance of a WCE (e.g., the WCE 102)and sent to the NED 140 and/or the network server 122 when wirelesspower transfer is requested. In some embodiments, the network server 122and/or an instance of NED (e.g., one of the NED 140, 160, 164) maydetect the presence and/or location of a WCE (e.g., the WCE 102), and inturn may generate the power charge message 170 on behalf of the WCE 102.In some embodiments, one instance of the power charge message 170 may beprovided to the network server 122 so that wireless power transfer canbe provided by one or more NEDs (e.g., any of the NEDs 140, 160, 164)that are ahead of the WCE 102. The power charge message 170 may be sentfrom the WCE 102 prior to the WCE 102 being within the power transferrange 149, 161 and/or 165 of one or more of the NEDs 140, 160, and/or164. Therefore, in some embodiments, the power charge message 170 may beused by the network server 122 to determine which of the NEDs 140, 160,and/or 164 is closest and/or should be used to provide wireless powertransfer. It is understood that the examples provided are forillustration purposes only, and therefore should not be construed aslimiting in any way.

In various embodiments, the operating environment 100 can include thenetwork 120 that can include, support, or otherwise communicate with aradio access network, such as the RAN 132. In some embodiments, at leasta portion of the network 120 and/or the RAN 132 can be associated with acommunications service provider. In various embodiments, the network 120can include an evolved packet core network, a core network, an IP-basednetwork, a transport network, an optical transport network, a circuitswitched network, a mobile Wide Area Network, a combination thereof, orthe like. It is understood that the network 120 can communicate with oneor more computing systems and/or devices that are external to thenetwork 120 (e.g., any of the WCEs 102, 118) via one or more networkaccess points that can establish, provide, and maintain wireless and/orwired communication links. In some embodiments, an instance of a networkaccess point, such as the network access point 152, can be provided orotherwise included within an instance of a network edge device, such asany of the NEDs 140, 160, and/or 164. It is understood that, in someembodiments, one or more instances of a network access point may providewired and/or wireless communicative coupling to any component of theoperating environment 100. In various embodiments, the network 120 maybe accessed via one or more instance of the RAN 132. In someembodiments, the RAN 132 and/or the network 120 can include one or moreinstances of a NED, such as any of the NEDs 140, 160, and/or 164, thathas an instance of the network access point 152 included therein. Invarious embodiments, an instance of the network access point 152 caninclude, but should not be limited to, one or more of a base transceiverstation, a wireless router, a femtocell, an Node B, an eNodeB, a gNodeB(i.e., an access point that incorporates New Radio access technology,such as LTE Advanced, and other 5G technology), a multi-standard metrocell node, an optical network terminal, and/or other network nodes orcombinations thereof that are capable of providing communication toand/or from the network 120. In some embodiments, the network 120 and/oran instance of the RAN 132 can include and support one or more of anevolved universal mobile telecommunications system (“UMTS”), aterrestrial radio access (“E-UTRAN”), a mobility management entity(“MME”), a serving/PDN gateway (“S/PGW”), a home subscriber server(“HSS”), an access and mobility function (“AMF”), a session managementfunction—user plane function (“SMF-UPF”), unified data management(“UDM”), a vehicle-to-everything (“V2X”) application server, anapplication function (“AF”), an enhanced mobile broadband system(“eMBBS”), a mobile edge computing (“MEC”) unit, a combination thereof,and/or any other systems, devices, and/or functions that may be includedin 2G, 3G, 4G, 5G, or later communication architecture. It should beunderstood that the examples provided are for illustration purposesonly, and therefore should not be construed as limiting in any way.

In various embodiments, the operating environment 100 can include atleast a portion of the power grid 130. The power grid 130 refers to oneor more energy harvesting and/or power source components that enablepower generation and/or wired power transmission from a power source(e.g., a power plant). It is understood that the power grid 130 mayharness energy from a variety of sources (e.g., solar, fossil fuels,wind, hydro-electric, etc.) as understood by one of ordinary skill inthe technology. In some embodiments, the power grid 130 can include orotherwise provide one or more power transmission cables that supportwired power transmission to any instance of a NED, such as any of theNEDs 140, 160, 164. As such, each of the NEDs 140, 160, 164 can serve asan edge device for wireless power transmission. In some embodiments, thepower grid 130 can provide information to and/or from the network 120 asto the amount of power that is being handled or otherwise transmitted byeach NED (e.g., any of the NEDs 140, 160, 164). By this, a communicationservice provider can provide a wireless power transmission service, suchas the WPT service 124 to WCEs (e.g., the WCEs 102, 118) that arealready clients of the network 120 and/or the RAN 132. It should beunderstood that the examples provided are for illustration purposesonly, and therefore should not be construed as limiting in any way.

In various embodiments, the operating environment 100 can include one ormore instance of the network server 122 that can support, host, execute,or otherwise facilitate operation of the WPT service 124. In variousembodiments, the WPT service 124 may be configured as a softwareplatform that is hosted by one or more computing systems to managelaser-based wireless power transfer to one or more WCEs (e.g., the WCEs102, 118). It is understood that the use of the term “service” isintended to correspond with one or more network operations that supporthandling of communications, messages, and/or instructions for wirelesspower transmission over the network 120 and/or the RAN 132. Therefore,any use of the term “service” in the claims shall not be construed orinterpreted as being direct to, involving, or otherwise including ajudicial exception (e.g., an abstract idea, an idea of itself, aneconomic process, etc.) or any other non-patentable subject matter. Assuch, use of the term “service” shall be construed within the realm oftechnology as understood by one of ordinary skill in technology. Itshould be understood that the examples provided are for illustrationpurposes only, and therefore should not be construed as limiting in anyway.

In various embodiments, the network server 122 can include one or moreinstance of a processing unit and/or processing circuitry, such as oneor more instance of a processor 121A. In various embodiments, aninstance of the processor 121A can be configured at least similar and/oridentical to an instance of a processing unit discussed below withrespect to FIG. 6. In various embodiments, the network server 122 caninclude one or more instance of a data storage device, such as a memory121B. In some embodiments, the memory 121B can include volatile and/ornon-volatile memory implemented in any method or technology for storageof information such as computer-executable instructions, datastructures, software program modules, or other data disclosed herein. Itis understood that, use of the term “memory” and “computer storagemedium” and variations thereof in the claims does not include, and shallnot be construed to include, a wave or a signal per se and/orcommunication media. The memory 121B can be configured substantiallysimilar to memory discussed further below with respect to FIG. 6. Itshould be understood that the examples provided are for illustrationpurposes only, and therefore should not be construed as limiting in anyway.

In various embodiments, the WPT service 124 of the network server 122can receive and/or detect the power charge message 170 from the WCE 102.In some embodiments, the WPT service 124 can analyze the contents of thepower charge message 170, such as but not limited to, an instance of theWCE identifier 108 and/or the location identifier 109. In variousembodiments, an instance of the WCE identifier 108 can be used tocompare against a power authorization map 126 to facilitatedetermination of whether the corresponding WCE (e.g., the WCE 102) isauthorized to receive wireless power transfer from one or more of theNEDs 140, 160, 164. In various embodiments, the power authorization map126 can include a plurality of authorized identifiers, such asauthorized identifiers 127A-N, that provide an identity of equipmentwhich are authorized and approved to use the WPT service 124, and thusreceive laser-based wireless power transfer from one or more of the NEDs140, 160, and/or 164. For example, in an embodiment where the WCE 102 isa client of the WPT service 124, then the WCE identifier 108corresponding to the WCE 102 will be found to correspond with one of theauthorized identifiers 127A-N of the power authorization map 126. Invarious embodiments, each instance of an authorized identifier fromamong the plurality of authorized identifiers 127A-N can correspond witha particular equipment profile, such as one of equipment profiles128A-N. Therefore, the power authorization map 126 can provide a pointerfrom one of the authorized identifiers 127A-N to a corresponding one ofthe equipment profiles 128A-N. In various embodiments, an instance of anequipment profile (e.g., any of the equipment profiles 128A-N) canindicate information about the associated WCE (e.g., the WCE 102), whichcan include, but should not be limited to, whether the associated WCEhas an instance of the adjustable laser photodetector 111, the equipmenttype of the associated WCE (e.g., an electric road vehicle, an air-basedvehicle, a user equipment such as a smart phone, etc.), historical powertransfer data (i.e., a historical power transfer log indicating when,where, and/or how much power was transferred to the associated WCE usingthe WPT service 124), and/or historical location data (i.e., historicallocation log of where the associated WCE has traveled or otherwise movedso as to facilitate determination of trends and/or predictions formovement).

In some embodiments, the power authorization map 126 can indicatewhether a particular WCE (e.g., any of the WCEs 102, 118) correspondswith an equipment priority flag, such as an equipment priority flag 125.An instance of the equipment priority flag 125 can indicate that acorresponding WCE should be prioritized to receive wireless powertransfer before other WCEs, and thus communications associated with thatcorresponding WCE should be handled with a higher priority than a WCEwithout the equipment priority flag 125. For example, in someembodiments, an instance of a WCE may be configured as equipment usedfor emergency operations (e.g., an ambulance, a police car, a firetruck, a rescue vehicle, device used my emergency rescue personnel,etc.), and therefore the WPT service 124 may assigned or otherwiseassociated with an instance of the equipment priority flag 125 with oneof the equipment profiles 128A-N that is associated with the WCEconfigured for emergencies. Therefore, in various embodiments, one ormore of the equipment profiles 128A-N of the power authorization map 126can include and/or point to an instance of the equipment priority flag125 when the associated WCE should receive high priority handling, andthus should be provided wireless power transfer before other WCEs thatdo not have an instance of the equipment priority flag 125.

In some embodiments, an instance of a WCE (e.g., the WCE 102) canprovide the WPT service 124 with a current charge profile, such as acurrent charge profile 172. For example, as illustrated in FIG. 1, theWCE 102 may provide any of the NED 140, the RAN 132, the network 120,and/or the network server 122 with an instance of the current chargeprofile 172. The current charge profile 172 can include an instance ofthe charge criticality indicator 110 and the current charge level 107.In some embodiments, the current charge level 107 may be measured interms of a percentage (e.g., from 0-100%, where 0% corresponds with afully depleted charge and 100% corresponds with a full charge) so as toindicate the relative charge level of the associated WCE at the timethat the current charge profile 172 and/or the current charge level 107was sent to the network server 122. In some embodiments, the WPT service124 may configure or otherwise provide a charge threshold 123. Thecharge threshold 123 can indicate a threshold which must be crossedbefore a particular WCE is allowed to engage or otherwise participate inwireless power transfer. For example, in some embodiments, the chargethreshold 123 can be a value between 0-100, and thus may be comparedagainst an instance of the current charge level 107. In someembodiments, the current charge level 107 must be below the chargethreshold 123 in order for the WCE to be allowed to receive wirelesspower transfer. For example, if the current charge level 107 indicatesthat the WCE 102 has a current charge of 50%, but the charge threshold123 is set to 20%, then the current charge level 107 is above the chargethreshold 123, and therefore the WCE 102 does not qualify to receivewireless power transfer at the current instance in time. The WPT service124 may ping or otherwise obtain updated information about an instanceof the current charge level 107 of the WCE 102. Therefore, once thecurrent charge level 107 crosses the charge threshold 123 (i.e., fallsbelow the charge threshold 123), then the corresponding WCE (e.g., theWCE 102) can be permitted to receive wireless power transfer.

In various embodiments, the network server 122 can store NED locationidentifiers, such as the NED location identifiers 129A-N, that includeinformation and/or identifiers pertaining to the location of variousNEDs (e.g., any of the NEDs 140, 160, 164) that support the WPT service124. For example, each of the NEDs 140, 160, 164 can operate in aparticular geographic location, and thus each of the NEDs 140, 160, 164can correspond with one of the NED location identifiers 129A-N. Forexample, in some embodiments, the NED 140 can correspond with the NEDlocation identifier 129A, which is included as one of the NED locationidentifiers 129A-N. In some embodiments, the WPT service 124 can use oneor more instances of the location identifier 109 provided by a WCE(e.g., the WCE 102) and/or historic location information included in acorresponding instance of one of the equipment profiles 128A-N tocompare against the NED location identifiers 129A-N, and in turndetermine which of the NEDs 140, 160, 164 should and/or could be used toimplement wireless power transfer. For example, if the locationidentifier 109 of the WCE 102 currently indicates that the location ofthe WCE 102 is closest to the NED location identifier 129A of the NED140, then the WPT service 124 may assign the NED 140 to the WCE 102, andinstruct at least the NED 140 to perform one or more operationsdiscussed herein to support wireless power transfer to the WCE 102.

In various embodiments, the operating environment can include one ormore NEDs that support and facilitate wireless power transfer, such asany of the NEDs 140, 160, and/or 164. In various embodiments, each ofthe NEDs 140, 160, 164 may be configured substantially similar to eachother. For clarity purposes, a discussion of the NED 140 is provided,however it is understood that any of the components of the NED 140 maybe included in other NEDs, such as the NEDs 160, 164. The NED 140 caninclude one or more of a wireless power transfer assembly (“WPTassembly”) 141, the network access point 152, a wireless power transfercontroller (“WPTC”) 150, a processor 154, and a memory 156. Theprocessor 154 can be configured substantially similar to a processingunit discussed with respect to FIG. 6. The memory 156 can be configuredsubstantially similar to memory discussed with respect to FIG. 6. TheWPTC 150 can be configured as software, a script, a module, and/or othercomputer executable instructions that can operate in coordination withthe WPT service 124 to facilitate wireless power transfer to a WCE, suchas the WCE 102. In various embodiments, the WPTC 150 can be executed bythe processor 154 so as to enable performance of one or more operationsdiscussed herein. In various embodiments, the NED 140 can include one ormore instances of the network access point 152 that can be configured asone or more of a base station, a NodeB, an evolved Node B (“eNB”), anext generation Node B (“gNB”) that support 5G New Radio standards, acombination thereof, or another network communication component thatsupports wireless communicative coupling with one or more WCEs, such asthe WCEs 102, 118. It should be understood that the examples providedare for illustration purposes only, and therefore should not beconstrued as limiting in any way.

In various embodiments, an instance of the WPT assembly 141 can includecomponents that enable laser-based wireless power transfer. For example,in some embodiments, the WPT assembly 141 can include one or moreinstance of an optical beamforming transmitter, such as the OBFT 142, arotational support structure 144, power adjustment components 146, andequipment detection components 148. The OBFT 142 can include a laseremitter (i.e., a laser transmitter that can generate the laser beam143), a beam expander, and a spatial light modulator that, in someembodiments, can be configurable to facilitate optical beamforming ofthe laser beam 143, such as based on one or more instructions from theWPTC 150, the WPT service 124, and/or elements of the WPT assembly 141.The OBFT 142 can be implemented to generate or otherwise provide aninstance of the laser beam 143 to facilitate and support laser-basedwireless power transfer. In some embodiments, the OBFT 142 may beconfigured so as to provide discontinuous wireless power transfer, suchas by providing the laser beam 143 in pulses (i.e., bursts of photons).In some embodiments, the OBFT 142 (e.g., via a laser transmittertherein) can provide bursts that are pulsed in time intervals measuredin milliseconds and/or nanoseconds. In various embodiments, an instanceof the OBFT 142 can provide a laser diode that directly convertselectrical energy into photons that are focused so as to produce aninstance of the laser beam 143. In some embodiments, the OBFT 142 can beconfigured to generate a laser beam at specific wavelengths, such as vialaser diode that provides a green laser beam (i.e., within the visiblespectrum for green light between 495-570 nanometers). It is understoodthat the OBFT 142 can be configured so as to generate an instance of thelaser beam 143 at other wavelengths within the ultraviolet spectrum, thevisible spectrum, and/or the infrared spectrum. In some embodiments, theOBFT 142 may be configured to mimic at least a portion of solarradiation (e.g., between 380-750 nanometer wavelength). Unlike microwavewireless power transfer mechanisms, the WPT assembly 141 can beconfigured so that the OBFT 142 can provide laser-based wireless powertransfer so that the power transfer range (e.g., the power transferranges 149, 161, 165) can span from tens of meters to hundreds ofmeters. It should be understood that the examples provided are forillustration purposes only, and therefore should not be construed aslimiting in any way.

In some embodiments, the WPT assembly 141 can include the rotationalsupport structure 144. The rotational support structure 144 can beconfigured to enable the OBFT 142 to rotate, which in turn can allow theOBFT 142 to track the movement of a WCE (e.g., the WCE 102). In someembodiments, the rotational support structure 144 can include verticaladjustment components that enable the OBFT 142 to adjust a verticalangle (i.e., tilt angle), thereby allowing the OBFT 142 to tilt up anddown so as to maintain a line of sight with the particular WCE (e.g.,the WCE 102). In some embodiments, the WPT assembly 141 can includepower adjustment components 146. The power adjustment components 146 caninclude motors, pistons, gears, belts, transceivers, circuitry, powersupplies, power converters, combinations thereof, and other componentsthat can receive instructions from one or more of the WPTC 150 and/orthe WPT service 124 to enable the OBFT 142 to activate the OBFT 142and/or enable movement of the rotational support structure 144.

In some embodiments, the WPT assembly 141 can include equipmentdetection components, such as the equipment detection components 148.The equipment detection components 148 can include one or more of aradar, ultrasonic sensor, video camera (e.g., visible and/or infraredoptical video camera), and/or laser detector. The equipment detectioncomponents 148 can be implemented so as to enable the WPT assembly 141to identify, determine, or otherwise detect when a WCE (e.g., the WCE102) is within the corresponding power transfer range (e.g., the powertransfer range 149) and/or where the WCE (e.g., the WCE 102) is locatedrelative to the OBFT 142. In various embodiments, the equipmentdetection components 148 may provide visual images and/or a video streamto the WPTC 150 and provide object recognition. By this, the WPTassembly 141 can distinguish the WCE 102 from the WCE 118, and targetthe appropriate WCE based on object recognition. For example, if the WCE102 requested wireless power transfer, but both the WCE 102 and the WCE118 are within the power transfer range 149, then the equipmentdetection components 148 can be activated to confirm that the WCE 102 iswithin the power transfer range 149, while also distinguishing the WCE102 from the WCE 118, thereby enabling the OBFT 142 to track the WCE 102and maintain line of sight for wireless power transmission. In variousembodiments, the equipment detection components 148 can enable the WPTassembly 141 to determine that a particular WCE (e.g., the WCE 102) isnot stationary because the equipment detection components 148 can detectthat the WCE 102 is moving within the power transfer range 149. In someembodiments, the WPTC 150 can determine that a WCE (e.g., the WCE 102)is not stationary within and/or outside of the power transfer range(e.g., the power transfer range 149) based on changes in instances ofthe location identifier 109 that are provided by the WCE (e.g., the WCE102). In some embodiments, the equipment detection components 148 can beimplemented to confirm a direct line of sight between the OBFT 142 andthe corresponding WCE that is the target of wireless power transmission(e.g., the WCE 102). For example, the equipment detection components 148may confirm that the adjustable laser photodetector 111 and/or the fixedphotodetector 112 is not obstructed from view, and thus the OBFT 142 hasa clear line of sight so that the laser beam 143 can be targeteddirectly to the particular WCE (e.g., the WCE 102).

In various embodiments, the WPT assembly 141 can activate the OBFT 142so as to provide wireless power transfer to a particular WCE (e.g., theWCE 102). When the OBFT 142 is activated, an instance of the laser beam143 can be emitted and targeted to the particular WCE (e.g., the WCE102). In some embodiments, the OBFT 142 can pulse the activation of theOBFT 142 so that the laser beam 143 is provided in bursts. In someembodiments, the power adjustment components 146 of the WPT assembly 141can adjust the time interval of pulses of the OBFT 142 so that the timebetween bursts is increased or decreased. Therefore, in instances whereadditional power is being requested or otherwise should be provided to aWCE (e.g., if a WCE corresponds with an equipment priority flag 125and/or provides a charge criticality indicator 110 requesting additionalpower transfer), the OBFT 142 can be adjusted so that the time intervalbetween pulses is decreased, thereby increasing the overall wirelesspower transfer to the particular WCE (e.g., the WCE 102). By this, thePBFT can dynamically adapt and be reconfigured to provide a specificamount of wirelessly transmitted power to a particular target WCE basedon the particular charge criticality indicator 110, while other WCE'smay receive different amounts of wireless power transfer. As such, insome embodiments, the OBFT 142 can be activated to provide wirelesspower transfer after the OBFT 142 is reconfigured and/or oriented basedon the charge criticality indicator 110 and the location of the targetWCE, such as provided by an instance of location identifier 109. It isunderstood that the examples discussed are for illustration purposesonly and should not be limiting in any way.

In various embodiments, the WPTC 150 and/or the WPT service 124 candetermine the direction 113 of the target WCE (e.g., the WCE 102) and,in turn, determine which one or more NEDs 140, 160, 164 should be usedto handle wireless power transfer. In some embodiments, the WPTC 150and/or the WPT service 124 can assign the NED 140 to be the first toprovide wireless power transfer to the WCE 102. Because the direction113 of the WCE 102 is towards the NEDs 160, 164 after the WCE 102 leavesthe power transfer range 149 of the NED 140, the WPT service 124 and/orthe WPTC 150 can instruct one or more of the NEDs 160, 164 to prepare toprovide wireless power delivery to the WCE 102 after the WCE 102 leavesthe power transfer range 149 of the NED 140, and/or upon the WCE 102entering the power transfer ranges 161, 165 of the NEDs 160, 164,respectively. In some embodiments, the NEDs 160, 164 may be considered“downstream” of the NED 140 because the NEDs 160, 164 would be put intoservice after the NED 140 is activated. In various embodiments the NEDs160, 164 can include components that are at least similar and/or thesame as the NED 140. Therefore, in various embodiments, one or moreinstances of the WPT assembly 141, the network access point 152, theWPTC 150, the processor 154, and/or the memory 156 can be included inthe NEDs 160, 164. Because one or more of the NEDs 160, 164 may beconsidered downstream or downrange of the NED 140, the correspondingcomponents within the NEDs 160, 164 may also be referred to asdownstream and/or downrange. For example, in an embodiment, the NED 160can include a downstream WPT assembly 162. The downstream WPT assembly162 can be substantially the same and/or identical to the WPT assembly141, and therefore the NED 160 can provide wireless power transfer tothe WCE 102 in a manner that is substantially similar and/or identicalto the operations discussed above with respect to the NED 140.

In various embodiments, the particular NED that is currently providingwireless power transmission may prepare other, downstream NEDs (e.g.,the NEDs 160, 164) for wireless power transfer to the WCE (e.g., the WCE102) before the target WCE (e.g., the WCE 102) leaves the current powertransfer range (e.g., the power transfer range 149 of the NED 140). Forexample, in some embodiments, the NED 140 can generate a chargepreparation command, such as any of charge preparation commands 180,182. An instance of a charge preparation command (e.g., any of thecharge preparation commands 180, 182) can be directed to another NEDthat is located outside of the current power transfer range, such as theNEDs 160, 164, respectively, that are located outside of the powertransfer range 149 of the NED 140. In some embodiments, the chargepreparation command (e.g., any of the charge preparation commands 180,182) can be directed to, or otherwise instruct, a wireless powertransfer assembly that is located within a downstream NED, such as thedownstream WPT assembly 162 that can be located within the NED 160. Thedownstream WPT assembly 162 includes another instance of the OBFT 142 toprovide wireless power transfer within the corresponding power transferrange (i.e., the power transfer range 161), which may lie inside and/oroutside of the power transfer range 149 of the NED 140 which currentlyserves the WCE 102. In some embodiments, a charge preparation command(e.g., any of the charge preparation commands 180, 182) can instruct acorresponding NED (e.g., the NEDs 160, 164) to prepare to providewireless power transfer to the WCE 102 by including the current locationinformation of the WCE 102 (e.g., one or more instance of the locationidentifier 109 of the WCE 102) and/or other configuration informationabout the OBFT 142 that is currently providing wireless powertransmission, such as the time period of the pulse for the laser beam143, so that the amount of energy being provided by each of the NEDs140, 160, 164 can be similar or otherwise match each other. In someembodiments, two or more of the NEDs 140, 160, 164 may concurrentlyprovide wireless power transfer to a single WCE (e.g., the WCE 102)while the WCE 102 is within each of the power transfer ranges at thesame time (e.g., the overlapping portions of the power transfer ranges149 and 161, or the overlapping portions of the power transfer ranges161 and 165).

In an embodiment, an instance of a WCE (e.g., the WCE 118) may includean instance of a WPT assembly (e.g., the WPT assembly 141). Inembodiments where the WCE includes an instance of the WPT assembly 141,the corresponding WCE may be physically coupled to an interface of thepower grid 130, and therefore may independently provide wireless powertransfer to other WCEs, such as the WCE 102. It should be understoodthat the examples provided are for illustration purposes only, andtherefore should not be construed as limiting in any way.

FIG. 1 illustrates the operating environment 100 having one or moreinstance of the WCE 102, the head unit 103, the TCU 104, the batterysystem 105, the rechargeable battery cell 106, the current charge level107, the WCE identifier 108, the location identifier 109, the chargecriticality indicator 110, the adjustable laser photodetector 111, therotatable base 111A, the physical adjustment unit 111B, the PSPC 111C,the fixed photodetector 112, the direction 113, the velocity 114, thenetwork 120, the network server 122, the processor 121A, the memory121B, the charge threshold 123, the WPT service 124, the equipmentpriority flag 125, the power authorization map 126, the authorizedidentifiers 127A-N, the equipment profiles 128A-N, the NED locationidentifiers 129A-N, the power grid 130, the RAN 132, the NED 140, theWPT assembly 141, the OBFT 142, the laser beam 143, the rotationalsupport structure 144, the power adjustment components 146, theequipment detection components 148, the power transfer range 149, theWPTC 150, the network access point 152, the processor 154, the memory156, the NED 160, the power transfer range 161, the downstream WPTassembly 162, the NED 164, the power transfer range 165, the powercharge message 170, the current charge profile 172, the adjustmentinstruction 174, the charge preparation command 180, and the chargepreparation command 182. It should be understood, however, that someimplementations of the operating environment 100 can include zero, one,or more than one instances of the above listed elements of the operatingenvironment 100 shown in FIG. 1. As such, the illustrated embodiment ofthe operating environment 100 is understood to be illustrative andshould not be construed as being limiting in any way.

Turning now to FIG. 2 with continued reference to FIG. 1, a blockdiagram 200 illustrating an instance of a vehicle 201 and aspectsthereof will be described, according to an illustrative embodiment. Itis understood that one or more instances of the WCE 102 and/or the WCE118 illustrated and discussed with respect to FIG. 1 can be configuredat least similar to the vehicle 201 shown and discussed with respect toFIG. 2. As such, in some embodiments, aspects of the vehicle 201 can beincluded in one or more instance of a wirelessly chargeable equipment(e.g., the WCE 102 and/or the WCE 118). The vehicle 201 shown in FIG. 2is illustrated for purposes of clarity of discussion, and therefore isprovided as an example. It is understood that zero, one, or more thanone instances of the components discussed herein with respect to thevehicle 201 may be implemented in various embodiments. As such, theexamples provided are for illustration purposes only, and thereforeshould not be construed as limiting in any way.

The illustrated vehicle 201 includes vehicle mechanical/electricalfunction components 202, a vehicle processor 203, a vehicle memory 204,a vehicle firmware 206, a vehicle operating system 208, a telematicscontrol unit 209, one or more vehicle software application(s) 210, avehicle head unit 211, a display 211A, an input/output component 211B, avehicle wireless communications component 212, an instance of a vehiclecommunication interface 218 that supports a direct transmission mode219, an instance of a network communication interface 220 that supportsthe network transmission mode 221, a vehicle dedicated short-rangecommunications (“DSRC”) component 214, and a cellularvehicle-to-anything (“C-V2X”) component 216. Each of these componentswill now be described in detail. It is understood that the termvehicle-to-anything (“V2X”) refers to a vehicle's communication ability(e.g., the vehicle 201) through components (e.g., a telematics controlunit) that are configured to communicate with one or more network ornetwork infrastructure, such as the network 120, the network server 122,and/or one or more of the NEDs 140, 160, 164. In some embodiments, acommunication that is sent to and/or from a vehicle may be referred toas the implementation of vehicle-to-everything (“V2X”) communications,which can include one or more of vehicle-to-vehicle (“V2V”)communications, vehicle-to-infrastructure (“V2I”) communications,vehicle-to-network (“V2N”) communications, and/or vehicle-to-pedestrian(“V2P”) communications, and may facilitate communicative couplingbetween vehicles, infrastructure, a network, and/or pedestrians,respectively. It is understood that the examples provided are forillustration purposes only, and therefore should not be construed aslimiting in any way.

The vehicle mechanical/electrical function components 202 can includemechanisms, circuitry, elements, and/or components of the vehicle 201that enable the vehicle to function and operate. For example, one ormore instances of the vehicle mechanical/electrical function components202 can include, an engine, a transmission, a braking system, atransmission control unit, an engine control unit, a battery system(e.g., an instance of the battery system 105), an electrical system, asafety system, a heating ventilation and air conditioning system, alighting system, a sensor system (e.g., a lane detection system, crashavoidance system, etc.), or any other component or element that mayfacilitate function of the vehicle 201 and/or support one or more of theoperations discussed herein. In various embodiments, the vehiclemechanical/electrical function components 202 can include one or morecomponents of the adjustable laser photodetector 111, the fixedphotodetector 112, the WPT assembly 141, a combination thereof, or thelike.

The vehicle processor 203 can include one or more hardware componentsthat perform computations to process data, and/or to executecomputer-executable instructions of one or more application programssuch as the vehicle software application(s) 210, one or more operatingsystems such as the vehicle operating system 208, other software, and/orthe vehicle firmware 206. In various embodiments, an instance of thevehicle processor 203 can be included in an instance of wirelesslychargeable equipment, such as the WCE 102. The vehicle processor 203 caninclude one or more central processing units (“CPUs”) and/or enginecontrol units (“ECU”) configured with one or more processing cores. Thevehicle processor 203 can include one or more graphics processing unit(“GPU”) configured to accelerate operations performed by one or moreCPUs, and/or to perform computations to process data, and/or to executecomputer-executable instructions of one or more application programs,operating systems, and/or other software that may or may not includeinstructions particular to graphics computations. In some embodiments,the vehicle processor 203 can include one or more discrete GPUs. In someother embodiments, the vehicle processor 203 can include CPU, ECU,and/or GPU components that are configured in accordance with aco-processing CPU/GPU computing model, wherein the sequential part of anapplication executes on the CPU and the computationally-intensive partis accelerated by the GPU. The vehicle processor 203 can include one ormore system-on-chip (“SoC”) components along with one or more othercomponents illustrated as being part of the vehicle 201, including, forexample, the vehicle memory 204, the vehicle wireless communicationscomponent 212, the DSRC component 214, or some combination thereof. Insome embodiments, the vehicle processor 203 can be or can include one ormore SNAPDRAGON SoCs, available from QUALCOMM of San Diego, Calif.; oneor more TEGRA SoCs, available from NVIDIA of Santa Clara, Calif.; one ormore HUMMINGBIRD SoCs, available from SAMSUNG of Seoul, South Korea; oneor more Open Multimedia Application Platform (“OMAP”) SoCs, availablefrom TEXAS INSTRUMENTS of Dallas, Tex.; one or more customized versionsof any of the above SoCs; and/or one or more proprietary SoCs. Thevehicle processor 203 can be or can include one or more hardwarecomponents architected in accordance with an ARM architecture, availablefor license from ARM HOLDINGS of Cambridge, United Kingdom.Alternatively, the vehicle processor 203 can be or can include one ormore hardware components architected in accordance with an x86architecture, such an architecture available from INTEL CORPORATION ofMountain View, Calif., and others. Those skilled in the technology willappreciate the implementation of the vehicle processor 203 can utilizevarious computation architectures, and as such, the vehicle processor203 should not be construed as being limited to any particularcomputation architecture or combination of computation architectures,including those explicitly disclosed herein.

The vehicle memory 204 can include one or more hardware components thatperform storage operations, including temporary or permanent storageoperations. In some embodiments, the vehicle memory 204 include volatileand/or non-volatile memory implemented in any method or technology forstorage of information such as computer-readable instructions, datastructures, program modules, the vehicle operating system 208, thevehicle firmware 206, the vehicle software application(s) 210, and/orother software, firmware, and/or other data disclosed herein. Computerstorage media includes, but is not limited to, random access memory(“RAM”), read-only memory (“ROM”), Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store data and which can be accessed by the vehicleprocessor 203. The vehicle memory 204 may be configured substantiallysimilar to memory 604 discussed with respect to FIG. 6. It is understoodthat one or more instances of the vehicle memory 204 can be included inone or more of the components of the vehicle 201 (and/or the WCE 102from FIG. 1), such as the vehicle head unit 211 (and/or the head unit103) and/or the telematics control unit 209 (and/or the telematicscontrol unit 104). As such, in the claims, the use of the phrase“vehicle memory” (or variations thereof) does not include waves orsignals per se and/or communication media.

The vehicle firmware 206, which in some embodiments may also be known asmicrocode, can be written onto a ROM of the vehicle memory 204. Thevehicle firmware 206 can be written on the ROM at the time ofmanufacturing and is used to execute programs on the vehicle processor203. In some embodiments, the vehicle firmware 206 includes the vehicleoperating system 208. In some embodiments, the vehicle firmware 206 isthe vehicle operating system 208. In some embodiments, the vehiclefirmware 206 and the vehicle operating system 208 are closely integratedfor performance of operations of the vehicle 201.

The vehicle operating system 208 can control the operation of at least aportion of the vehicle 201. In some embodiments, the vehicle operatingsystem 208 includes the functionality of the vehicle firmware 206 and/orthe vehicle software application(s) 210. The vehicle operating system208 can be executed by the vehicle processor 203 to cause the vehicle201 to perform various operations. The vehicle operating system 208 caninclude, by way of example without limitation, a member of the SYMBIANOS family of operating systems from SYMBIAN LIMITED; a member of theWINDOWS OS, WINDOWS MOBILE OS, and/or WINDOWS PHONE OS families ofoperating systems from MICROSOFT CORPORATION; a member of the PALM WEBOSfamily of operating systems from HEWLETT PACKARD CORPORATION; a memberof the BLACKBERRY OS family of operating systems from RESEARCH IN MOTIONLIMITED; a member of the IOS family of operating systems, a memory ofthe CARPLAY family of operating systems, and/or a member of the OS Xfamily of operating systems from APPLE INC.; a member of the ANDROID OSfamily and/or the ANDROID AUTO family of operating systems from GOOGLEINC.; an open-source software operating system build around the LINUXkernel; a member of a real-time operating system; a member of a portableoperating system interface automotive open system architecture and/orother operating systems. These operating systems are merely illustrativeof some contemplated operating systems that may be used in accordancewith various embodiments of the concepts and technologies describedherein and therefore should not be construed as being limiting in anyway. The vehicle software application(s) 210 can execute on top of thevehicle operating system 208. The vehicle software application(s) 210can be executed by the vehicle processor 203 to cause the vehicle 201(and/or components thereof, such as the vehicle head unit 211 and/or thetelematics control unit 209) to perform various operations describedherein. For example, the vehicle software application(s) 210 can be partof a vehicle entertainment system, a vehicle navigation system, avehicle “ECU”, and/or another computing system of the user vehicle. Insome embodiments, the vehicle software application(s) 210 can includeone or more instances of the applications that interact or otherwisecommunicate with the WPT service 124 and/or the WPTC 150 for wirelesspower transfer, according to various aspects discussed with respect toFIG. 1.

In some embodiments, the telematics control unit 209 may include and/orcontrol the vehicle wireless communications components 212 discussedbelow. In some embodiments, the TCU 104 discussed with respect to FIG. 1may be configured substantially similar to the telematics control unit209. The telematics control unit 209 can include one or more instancesof the vehicle processor 203, the vehicle memory 204, the vehicleoperating system 208, and/or the vehicle firmware 206. The telematicscontrol unit 209 may be configured to control the inflow and/or outflowof communications to and/or from the vehicle 201 via one or more of thevehicle wireless communications components 212. In various embodiments,the telematics control unit 209 can control, provide, and/or facilitatewireless tracking, wireless diagnostics, device pairing, crashnotification, and other communication to/from the vehicle 201. Invarious embodiments, the telematics control unit 209 can includecircuitry that operates as a network interface controller and canprovide communication to the vehicle head unit 211 and/or one or morevehicle software application(s) 210. In various embodiments, thetelematics control unit 209 can perform one or more functions and/oroperations discussed herein, such as but not limited to operationsdiscussed with respect to FIG. 1, FIG. 3, and/or FIG. 4.

The head unit 103 discussed above with respect to FIG. 1 may beconfigured substantially similar to the vehicle head unit 211. In someembodiments, the vehicle head unit 211 can include the display 211A thatcan be configured to present and/or provide audio output and/or videooutput via one or more user interface. The display 211A of the vehiclehead unit 211 can have a display device that presents various userinterfaces, requests, messages, and/or any other information (e.g., anyof the messages, commands, requests, responses, and/or identifiers fromFIG. 1) to a user or other occupant associated with the vehicle 201. Insome embodiments, the input/output component 211B can provide a usertouch-screen, audio speakers, microphones, haptic feedback system, orother input and/or output device or component that can alert a user tovarious communications. As such, an instance of the input/outputcomponent 211B and/or the display 211A can be implemented to enable theinput to be provided to the head unit 103 of the WCE 102.

The vehicle wireless communications component 212 can include one ormore wireless wide area network (“WWAN”) components (e.g., radiotransceivers, antenna, etc.) capable of facilitating communication withone or more WWANs, such as the network 120 and/or the RAN 132. In someembodiments, one or more instances of the vehicle wirelesscommunications component 212 can be configured to provide multi-modewireless connectivity. For example, the vehicle wireless communicationscomponent 212 may be configured to provide connectivity to the network120 and/or the RAN 132 and may provide functions in accordance withUMTS, LTE, 5G and New Radio standards, or via some other combination oftechnologies, and more particularly, one or more technologies thatsupport cell broadcast functionality. In various embodiments, thevehicle wireless communications component 212 can include one or moreinstances of a transceiver, sensors, cameras, circuitry, antennas, andany other components that can support and facilitate sending and/orreceiving communications over the vehicle communication interface 218using the direct transmission mode 219 and/or the network communicationinterface 220 using the network transmission mode 221. In someembodiments, the vehicle communication interface 218 can be providedand/or hosted by the DSRC component 214 and/or the C-V2X component 216.

The direct transmission mode 219 refers to a communication routine(which may be executed by the telematics control unit 209) by which avehicle can communicate messages to/from another device (while withineach other's communication range) without the messages being passedthrough an intermediary device of the network (e.g., without beinghandled by any of the network edge devices 140, 160, 164). In someembodiments, the direct transmission mode 219 can be provided over an802.11x protocol (e.g., 802.11p or protocol within the 802.11 family ofwireless local area network standards), which in some embodiments may bereferred to as protocols and/or standards for dedicated short-rangecommunications (“DSRC”). In some embodiments, the direct transmissionmode 219 can be provided using specifications pertaining to cellular V2X(“C-V2X”), which is initially defined by the Third GenerationPartnership Project (“3GPP”) Release 14, discussed in Release 15 andlater. In various embodiments, standards and protocols of C-V2X mayallow communication components to be configured to support the directtransmission mode 219 (e.g., via a PC5 interface) and the networktransmission mode 221 (e.g., via a Uu interface). The vehiclecommunication interface 218 can be configured to use, support, andprovide the direct transmission mode 219, and the network communicationinterface 220 can be configured to use, support, and provide the networktransmission mode 221. In various embodiments, the network transmissionmode 221 refers to a vehicle communication routine (which may beexecuted by the telematics control unit 209) by which the vehiclewireless communications component 212 uses and communicates with networkinfrastructure (e.g., network edge devices of the network 120 and/or theRAN 132) to transmit various communications that are directed to one ormore device through an access point of the network (i.e., networkinfrastructure), such as an instance of the network access point 152that can be included in the NED 140, the NED 160, and/or the NED 164. Insome embodiments, one or more instances of a communication (e.g., any ofthe power charge message 170, the current charge profile 172, theadjustment instruction 174, the charge preparation command 180, and/orthe charge preparation command 182) may be generated and/or receivedwith a configuration that facilitates and supports the use of thenetwork transmission mode 221.

The DSRC component 214 can be a radio communications device and/orcircuitry that can send and receive various communications (not shown)using the direct transmission mode 219. In some embodiments, the DSRCcomponent 214 is configured to operate within a 5.9 GHz radio frequencyband as defined by the United States Department of Transportation. Insome embodiments, the DSRC component 214 is configured to operate withinother radio frequency bands. In some embodiments, the DSRC component 214can operate using 802.11p or other technology.

The C-V2X component 216 can be a radio communications device and/orcircuitry that can send and receive V2X communications using the directtransmission mode 219 and/or the network transmission mode 221. In someembodiments, the C-V2X component 216 can operate in accordance with 3GPPRelease 14 or later. The C-V2X component 216 can support and provide thevehicle communication interface 218 and/or the network communicationinterface 220. In various embodiments, the C-V2X component 216 can beconfigured to support 5G New Radio transmissions and directcommunication transmissions so that communications may occur withinand/or outside of a direct communication range. In some embodiments, theC-V2X component 216 can transmit and receive communications over thedirect transmission mode within an ITS spectrum, such as a 5.9 GHz ITSband. In some embodiments, the C-V2X component 216 can providetransmission latency that is no more than a defined amount ofmilliseconds (e.g., less than 10 milliseconds). In some embodiments, theTCU 209 can include, and/or be configured to invoke, the C-V2X component216 and/or the DSRC component 214. It should be understood that theembodiment of the vehicle 201 illustrated in FIG. 2 is provided as anexample of a possible implementation of the WCE 102 and/or the WCE 118discussed with respect to FIG. 1. The examples provided are forillustration purposes only, and therefore should not be construed aslimiting in any way.

Turning now to FIGS. 3 and 4 with continued references to FIGS. 1 and 2,aspects of a method 300 and a method 400 for embodiments pertaining toaspects of connected vehicle network access optimization will bedescribed in detail, according to various illustrative embodiments. Itshould be understood that each of the operations of the one or moremethods disclosed herein (e.g., the method 300 and/or the method 400discussed below) are not necessarily presented in any particular orderand that performance of some or all of the operations in an alternateorder(s) is possible and is contemplated. It is also understood that anyof the operations from the methods disclosed herein may be combined orotherwise arranged to yield another embodiment of a method that iswithin the scope of the concepts and technologies discussed herein. Theoperations have been presented in the demonstrated order for ease ofdescription and illustration, and therefore should not be construed aslimiting the various embodiments disclosed herein. Operations may beadded, omitted, and/or performed simultaneously and/or sequentially,without departing from the scope of the concepts and technologiesdisclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions storedand included on a computer storage medium, as defined herein. Thephrases “computer executable instructions,” and variants thereof (e.g.,“computer-readable instructions”), as used herein, is used expansivelyto include routines, applications, modules, scripts, programs, plug-ins,data structures, algorithms, and the like. It is understood that any useof the term “module” (in the specification and claims) refers to adefined, callable set of computer-readable and executable instructionsthat, upon execution by a processor, configure at least a processor toperform at least a portion of one or more operations and functionsdiscussed herein so as to transform, upon execution, processingresources and/or memory resources into a particular, non-generic,machine. Computer-readable instructions can be implemented on varioussystem configurations including but not limited to one or more ofsingle-processor or multiprocessor systems, minicomputers, userequipment, mainframe computers, personal computers, network servers,hand-held computing devices, microprocessor-based, programmable consumerelectronics, a network platform, edge devices, vehicles, combinationsthereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system so as to provide a particular, non-generic machinedevice. The implementation is a matter of choice dependent on theperformance and other requirements of the computing system. Accordingly,the logical operations described herein are referred to variously asstates, operations, structural devices, acts, functions, instructions,and/or modules. These states, operations, structural devices, acts,functions, instructions, and/or modules may be implemented in software,in firmware, in special purpose digital logic, and any combinationthereof. As used herein, the phrase “cause a processor to performoperations” and variants thereof is used to refer to causing andtransforming a processor of a computing system or device, such as anycomponent within one or more of the WCE 102, the WCE 118, the network120, the RAN 132, network server 122, the NED 140, the NED 160, and/orthe NED 164, to perform one or more operations and/or causing one ormore instances of a processor to direct other components of a computingsystem or device, to perform one or more of the operations.

For purposes of illustrating and describing the concepts of the presentdisclosure, one or more of the operations of methods disclosed hereinare described as being performed by one or more instance of the NED 140via execution of one or more computer-readable instructions configuredso as to instruct and transform a processor, such as the WPTC 150 thatcan configure the processor 154. In some embodiments, one or moreoperations may be performed by one or more of the network server 122,the WPT assembly 141, the network access point 152, the NED 160, and/orthe NED 164. It should be understood that additional and/or alternativedevices and/or network infrastructure devices can, in some embodiments,provide the functionality described herein via execution of one or moreroutines, applications, and/or other software including, but not limitedto, the WPT service 124, the vehicle software application(s) 210, thevehicle firmware 206, the vehicle operating system 208, and/or any othercomputer executable instructions that can configure a device discussedherein, such as but not limited to one or more of the network server122, WCE 102, the WCE 118, the NED 140, the NED 160, and/or the NED 164.Thus, the illustrated embodiments are illustrative, and should not beviewed as being limiting in any way.

In various embodiments, one or more instances of a computer systemassociated with the WPT service 124 may execute so as to cause one ormore processor (e.g., an instance of the processor 121 and/or theprocessor 154) to perform at least a portion of one or more operationsdiscussed herein. In various embodiments, execution of the WPTC 150 cancause one or more instances of a NED 140 (and any components therein,such as the WPT assembly 141 and/or the network access point 152) toperform one or more operations discussed herein. It should be understoodthat the examples provided are for illustration purposes only, andtherefore should not be construed as limiting in any way. The method 300and the method 400 will be described with reference to one or more ofthe FIGS. 1 and 2.

Turning now to FIG. 3, the method 300 can begin and proceed to operation302, where the NED 140 can receive a power charge message, such as thepower charge message 170. In some embodiments, the power charge message170 may be provided to the NED 140 directly from a WCE which isrequesting wireless power transfer, such as the WCE 102. In someembodiments, the power charge message 170 may have been sent to thenetwork server 122 by way of another instance of the network accesspoint 152 and/or the network 120, and therefore the NED 140 may receivethe power charge message 170 from the network server 122. In variousembodiments, the power charge message 170 corresponds to one or moreinstances of a WCE that is requesting or otherwise is capable ofreceiving laser-based wireless power transfer to charge a battery systemof the WCE, such as the WCE 102 that can engage in the laser-basedwireless power transfer to recharge the rechargeable battery cell 106 ofthe battery system 105. In some embodiments, the power charge message170 can include a wirelessly chargeable equipment identifier and alocation identifier corresponding to the WCE that is capable ofreceiving laser-based wireless power transfer, such as the WCEidentifier 108 and the location identifier 109 corresponding to the WCE102.

From operation 302, the method 300 can proceed to operation 304, wherethe WPTC 150 can determine whether a WCE (e.g., the WCE 102) requestingwireless power transfer is authorized to receive the wireless powertransfer. In some embodiments, the WPTC 150 may have access to, orotherwise utilize, the power authorization map 126 that can bemaintained by the WPT service 124 of the network server 122. The WPTC150 can compare the WCE identifier 108 corresponding to the requestingWCE (i.e., the WCE 102) with the authorized identifiers 127A-N of thepower authorization map 126, where the authorized identifiers 127A-Nindicate that a corresponding WCE is authorized to receive wirelesspower transfer. In some embodiments, one or more other operations may beperformed before wireless power transfer is actually provided, such asoperations discussed with respect to method 400 provided below. In someembodiments, if the WPTC 150 and/or the WPT service 124 determines thatthe WCE identifier 108 matches or otherwise corresponds with one of theauthorized identifiers 127A-N, then the corresponding WCE (e.g., the WCE102) is authorized to receive wireless power transfer. Responsive todetermining that the WCE 102 is authorized to receive wireless powertransfer, the method 300 can proceed along the YES path to operation308, which will be discussed below. In some embodiments, if the WPTC 150and/or the WPT service 124 determines that the WCE identifier 108 doesnot match or otherwise cannot be found to correspond with one of theauthorized identifiers 127A-N, then the corresponding WCE (e.g., the WCE102) may not yet be authorized to receive wireless power transfer. Insome embodiments, responsive to determining that the WCE 102 is notauthorized and/or not yet authorized to receive wireless power transfer,the method 300 may proceed along the NO path to operation 306. In someembodiments, one or more operations discussed with respect to method 400may occur prior to and/or concurrent with operation 304, such asoperation 404 and/or operation 406. Therefore, it is understood that theexamples provided are for illustration purposes only, and thereforeshould not be construed as limiting in any way. For clarity purposes adiscussion of the method 300 proceeding along the NO path to operation306 will be provided first, followed by a discussion proceeding alongthe YES path to operation 308.

At operation 306, the WPTC 150 can redirect the particular WCEcorresponding to the power charge message 170 (e.g., the WCE 102) to theWPT service 124 so as to allow the WCE 102 to become a client of the WPTservice 124, and in turn become authorized to engage in laser-basedwireless power transfer. In some embodiments, the WPT service 124 canprovide, host, and/or maintain a portal by which the WCE 102 can accessand become a client of the WPT service 124, which in turn can cause theWPT service 124 to instantiate the WCE identifier 108 of the WCE 102among the authorized identifiers 127A-N. In some embodiments, responsiveto redirecting the WCE 102 to the WPT service 124 to obtainauthorization, the method 300 may proceed from operation 306 tooperation 304 discussed above. In some embodiments, the method 300 mayproceed from operation 306 to operation 330, where the method 300 mayend.

Returning to operation 304, in some embodiments, the method 300 mayproceed along the YES path to operation 308, where the WPTC 150 canobtain a current charge profile corresponding to the particular WCE,such as the current charge profile 172 corresponding to the WCE 102. Insome embodiments, the current charge profile 172 can include one or moreinstances of the charge criticality indicator 110 and the current chargelevel 107 of the WCE 102. In some embodiments, the current chargeprofile 172 may be obtained directly from the WCE 102, from the networkserver 122, and/or via the network 120. In some embodiments, the currentcharge profile 172 can be used to determine the priority of delivery ofwireless power transfer to the WCE 102. In some embodiments, WPTC 150can configure the OBFT 142 so as to adjust how wireless power transferis delivered based on the current charge profile 172. In someembodiments, one or more operations pertaining to the method 400 fromFIG. 4 may be performed in addition to any operation discussed withrespect to the method 300. Further discussion of operations pertainingto the method 400 are discussed below with respect to FIG. 4.

In various embodiments, the method 300 can proceed to operation 310,where the WPTC 150 can determine whether the WCE 102 is within a powertransfer range of the particular NED that is assigned to providewireless power transfer to the WCE 102. For example, the WPTC 150 and/orthe WPT service 124 may determine that the NED 140 is closest to the WCE102 and/or will intercept the path of the WCE 102, and therefore the WPTservice 124 may assign or otherwise designate the NED 140 to service theWCE 102. Therefore, in some embodiments, the NED 140 may determinewhether the WCE 102 is within the power transfer range 149, whichcorresponds to the coverage area that laser-based wireless powertransfer can be provided by the NED 140.

In some embodiments, if the NED 140 determines that the WCE 102 is notwithin the power transfer range 149, then the method 300 can proceedalong the NO path to operation 312, where the NED 140 can prepare forwhen the WCE 102 is within the power transfer range 149 of the NED 140.For example, the NED 140 can use one or more instances of the locationidentifier 109 and/or the corresponding instance of an equipment profile(e.g., from among the equipment profiles 128A-N) to determine thedirection 113 and velocity 114 of the WCE 102, thereby enabling the NED140 to determine an estimated time which the WCE 102 will arrive withinthe power transfer range 149. In some embodiments, the WPT assembly 141of the NED 140 may adjust the OBFT 142 to be oriented in a direction ofthe WCE 102, thereby maximizing the amount of laser-based wireless powertransfer while the WCE 102 is within the power transfer range 149. Insome embodiments, from operation 312, the method 300 may continue tomonitor or otherwise determine whether the WCE 102 has entered the powertransfer range 149, and therefore the method 300 may proceed back tooperation 310.

Returning to operation 310, in some embodiments, if the NED 140determines that the WCE 102 is within the power transfer range 149, thenthe method 300 can proceed along the YES path to operation 314, wherethe NED 140 can determine whether the WCE 102 is stationary (i.e., notmoving within the power transfer range 149 of the NED 140). In someembodiments, the NED 140 can determine whether the WCE 102 is stationaryor not stationary (i.e., moving or not moving) based on one or moreinstances of the location identifier 109 and/or historical locationinformation in a corresponding instance of an equipment profile from theequipment profiles 128A-N. For example, if the latest instance of thelocation identifier 109 provides geographic information indicating thatthe WCE 102 is within the geographic range provided by the powertransfer range 149 of the NED 140, then the WCE 102 may be considered tobe within the power transfer range 149. Therefore, if multiple instancesof the location identifier 109 corresponding to the WCE 102 are receivedby the NED 140 and indicate multiple different geographic positionswithin the power transfer range 149, then the NED 140 may determine thatthe WCE 102 is not stationary within the power transfer range 149.Similarly, if instances of the location identifier 109 does not changeover time, and thus the geographic location remains within the powertransfer range 149 without changing, then the NED 140 can determine thatthe WCE 102 is stationary within the power transfer range 149. In someembodiments, the NED 140 may implement or otherwise activate one or moreof the equipment detection components 148, which can include activatinga video camera to detect and identify the WCE 102. If the equipmentdetection components 148 identifies the WCE 102 (e.g., based on imageanalysis and object recognition) and determines that the WCE 102 iswithin the power transfer range 149, then the equipment detectioncomponents 148 may determine whether there is a change in the geographicposition of the WCE 102, which in turn enables determination of whetherthe WCE 102 is stationary or not stationary.

Therefore, in various embodiments, if the NED 140 determines that theWCE 102 is stationary, then the method 300 may proceed along the YESpath from operation 314 to operation 322, which will be discussed belowin further detail. Returning to operation 314, in some embodiments, ifthe NED 140 determines that the WCE 102 is not stationary, then themethod 300 can proceed along the NO path from operation 314 to operation316. For clarity purposes a discussion of the method 300 proceedingalong the NO path (i.e., based on a determination that the WCE 102 isnot stationary and thus moving within the power transfer range 149) tooperation 316 will be provided first, followed by a discussion below ofoperation 322.

At operation 316, in some embodiments, the NED 140 may determine whetherthe WCE 102 has an instance of the adjustable laser photodetector 111.In some embodiments, the WCE 102 may indicate the presence of theadjustable laser photodetector 111 within the power charge message 170.In some embodiments, an equipment profile corresponding to the WCE 102(e.g., form among the equipment profiles 128A-N) can indicate whetherthe WCE 102 is configured to have the adjustable laser photodetector111. In various embodiments, if the NED 140 determines that the WCE 102does not have an instance of the adjustable laser photodetector 111,then the NED 140 can identify and locate the presence of an instance ofthe fixed photodetector 112 on the WCE 102. In some embodiments, if theNED 140 determines that the WCE 102 has or is otherwise configured withthe adjustable laser photodetector 111, then the method 300 can proceedalong the YES path from operation 316 to operation 318. In someembodiments, if the NED 140 determines that the WCE 102 does not have oris otherwise not configured with the adjustable laser photodetector 111,then the method 300 can proceed along the NO path from operation 316 tooperation 320. For clarity purposes, a discussion of the method 300proceeding along the YES path to operation 318 will be provided first,followed by a discussion of operation 320.

At operation 318, the NED 140 can prepare and provide the adjustmentinstruction 174 to the WCE 102 based on the WCE 102 having theadjustable laser photodetector 111. In some embodiments, the adjustmentinstruction 174 can provide the WCE 102 with location information of theNED 140 (e.g., the NED location identifier 129A). The adjustmentinstruction 174 can command the adjustable laser photodetector 111(e.g., specifically the physical adjustment unit 111B) to reorient thePSPC 111C in a direction that faces or is otherwise pointed towards theNED 140. In some embodiments, the adjustment instruction 174 can commandthe physical adjustment unit 111B to rotate the PSPC 111C towards theOBFT 142 of the NED 140, and/or can instruct the adjustable laserphotodetector 111 to adjust a vertical angle of the PSPC 111C so thatthe PSPC 111C is tilted up towards (and thus faces) the OBFT 142 of theNED 140. In some embodiments, the adjustment instruction 174 caninstruct the adjustable laser photodetector 111 to maintain a line ofsight between the OBFT 142 and the WCE 102, thereby optimizinglaser-based wireless power transfer. From operation 318, the method 300may proceed to operation 320, which is discussed below in furtherdetail.

At operation 320, the NED 140 can track the movement of the WCE 102before, during, and/or after the WCE 102 is within the power transferrange 149 of the NED 140. Specifically, while the WCE 102 is within thepower transfer range 149, the NED 140 can activate the equipmentdetection components 148 to determine and confirm the speed, direction,and location of the WCE 102, which in turn can enable the WPT assembly141 to adjust the movement of the OBFT 142 so as to follow the movementof the WCE 102. By this, the OBFT 142 may be able to provide targeted,direct laser-based wireless power transfer to the WCE 102, whilepreventing or otherwise avoiding wireless power transfer to another WCE(besides the WCE 102) that is within the power transfer range 149.Therefore, the NED 140 can provide individual wireless power transferover extended distances (e.g., from tens of meters to hundreds ofmeters) to the WCE 102 while within the power transfer range 149.

From operation 320, the method 300 may proceed to operation 322, wherethe NED 140 may confirm a direct line of sight between the WCE 102 andthe OBFT 142. The NED 140 may activate the equipment detectioncomponents 148 to confirm that the WCE 102 is not obstructed fromreceiving wireless power transfer. For example, in an embodiment, if anobject (e.g., a tree, building, person, another WCE, etc.) is physicallyblocking (partially or fully) the adjustable laser photodetector 111and/or the fixed photodetector 112, then the NED 140 would not be ableto confirm that line of sight exists between the OBFT 142 and the WCE102. Therefore, the NED 140 may continue to check whether an obstructionexists between the OBFT 142 and the WCE 102. The NED 140 can confirmthat line of sight exists between the OBFT 142 and the WCE 102 when theadjustable laser photodetector 111 and/or the fixed photodetector 112 isnot obstructed from view of the OBFT 142. In some embodiments, the OBFT142 may be activated and/or authorized to be activated responsive toconfirming a direct line of sight between the OBFT 142 and the WCE 102.In some embodiments, the method 300 may proceed from operation 322 tooperation 324, which will be discussed below in further detail. In someembodiments, operation 324 may be performed concurrent with operation322. In some embodiments, the method 300 may proceed from operation 322to operation 328. For clarity purposes, a discussion of operation 324will be provided first, followed by a discussion of operation 328.

At operation 324, the NED 140 can generate an instance of a chargepreparation command that can be directed to another NED that is locateddownstream of the WCE 102, such as any of the charge preparationcommands 180, 182 that can be directed to the NEDs 160, 164,respectively, which are downstream from the NED 140. In someembodiments, the NED 140 can generate an instance of a chargepreparation command (e.g., any of the charge preparation commands 180,182) prior to the WCE 102 leaving the power transfer range 149corresponding to the NED 140 and/or before the WCE 102 enters the powertransfer range of the downstream NED, such as before entering the powertransfer range 161 of the NED 160 and/or the power transfer range 165 ofthe NED 164. In some embodiments, an instance of a charge preparationcommand (e.g., any of the charge preparation commands 180, 182) can bedirected for use by another instance of the WPT assembly 141 that can belocated in the downstream NED, such as the downstream WPT assembly 162of the NED 160. In various embodiments, the downstream WPT assembly 162can include another OBFT (e.g., another instance of the OBFT 142) toprovide wireless power transfer to the WCE 102. In some embodiments, thedownstream WPT assembly 162 of the NED 160 can provide wireless powertransfer to the WCE 102 while the NED 140 is currently providingwireless power transfer (i.e., both the WPT assembly 141 and thedownstream WPT assembly 162 can concurrently generate separate instancesof the laser beam 143 to provide wireless power transfer directly to theWCE 102) because the power transfer range 161 corresponding to the NED160 may overlap with the power transfer range 149 corresponding to theNED 140. In some embodiments, the WPT assembly 162 may provide wirelesspower transfer to the WCE 102 once the WCE 102 leaves the power transferrange 149 of the NED 140 and is within the power transfer range 161 ofthe NED 160. In various embodiments, an instance of the chargepreparation command (e.g., the charge preparation commands 180, 182) caninstruct a downstream wireless power transfer assembly (e.g., thedownstream WPT assembly 162) to prepare to provide wireless powertransfer to the WCE 102, such as by providing current velocity,direction, and/or location information of the WCE 102 while the WCE 102is within the power transfer range 149 of the NED 140.

From operation 324, the method 300 can proceed to operation 326, wherethe NED 140 can provide an instance of the charge preparation command(e.g., the charge preparation commands 180, 182) to another NED thatincludes a downstream wireless power transfer assembly (and thus anotherOBFT that provides wireless power transfer). For example, in someembodiments, the charge preparation command 180 can be provided to theNED 160 and the charge preparation command 182 can be provided to theNED 164. In various embodiments, each of the NEDs 160, 164 are elementsthat provide laser-based wireless power transfer for the WPT service124, and therefore may coordinate one or more operations between variousNED (e.g., any of the NEDs 140, 160, 164) so as to share informationand/or data as to current and/or previous operations of wireless powertransfer for a particular WCE (e.g., the WCE 102). In some embodiments,the method 300 may proceed from operation 326 to operation 330, wherethe method 300 may end. In some embodiments, the method 300 can proceedfrom operation 326 to operation 328.

At operation 328, the NED 140 may activate the OBFT 142 that generatesthe laser beam 143 and provides laser-based wireless power transfer tothe WCE 102 while the WCE 102 is within the power transfer range 149 ofthe NED 140. In some embodiments, the NED 140 can configure or otherwiseactivate the OBFT 142 so as to provide bursts of wireless powertransfer, such as by pulsing the OBFT 142 so that the laser beam 143(and thus the wireless power transfer) is discontinuous. In someembodiments, the NED 140 can adjust the time interval between pulses ofthe OBFT 142 so that the amount of power transfer provided can beincreased and/or decreased based on the length of the time interval. Forexample, a shorter time interval between pulses of the OBFT 142 canincrease the amount of wireless power transfer to the WCE 102, whileincreasing the time interval between pulses of the OBFT 142 can decreasethe amount of wireless power transfer to the WCE 102. Further discussionof possible embodiments are provided with respect to method 400illustrated in FIG. 4.

From operation 328, the method 300 can proceed to operation 330, wherethe method 300 may end. The method 300 may, in various embodiments,proceed to or include one or more operations of the method 400, which isdiscussed below with respect to FIG. 4. In some embodiments, one or moreof the operations of the method 300 may be performed by the NED 140(e.g., by any components included therein, such as but not limited tothe WPTC 150, the WPT assembly 141, the OBFT 142, the network accesspoint 152, etc.) so as to cause another NED (e.g., the NED 160 and/orthe NED 164) and/or an element thereof (e.g., a downstream WPT assembly162, which in turn can include another instance of the OBFT 142) toperform one or more of the operations discussed herein. It should beunderstood that the examples provided are for illustration purposesonly, and therefore should not be construed as limiting in any way.

Turning now to FIG. 4, the method 400 for facilitating wireless powertransfer network management is disclosed, according to an illustrativeembodiment. In an embodiment, the method 400 can be performed by any ofa plurality of network edge devices, such as any of the NED 140, the NED160, and/or the NED 164. Instances of the processor 154 can be executedand configured, at least in part, by an instance of the WPTC 150 and/orthe WPT service 124. For clarity purposes, the method 400 will bedescribed as being performed by the NED 140, although it is understoodthat this may not necessarily be the case for all embodiments. It isunderstood that, in various embodiments, one or more of the operations,in whole or in part, may be performed by an instance of a network edgedevice (e.g., any of the NEDs 140, 160, and/or 164), the network server122, and/or components included therein (e.g., the WPTC 150, the WPTassembly 141, the OBFT 142, the network access point 152, etc.). Itshould be understood that the examples provided are for illustrationpurposes only, and therefore should not be construed as limiting in anyway.

In some embodiments, the method 400 can begin at operation 402, wherethe WPTC 150 and/or the WPT service 124 can identify the particular WCEthat is requesting wireless power transfer, such as the WCE 102. Forexample, the WPTC 150 can analyze the WCE identifier 108 that isincluded in the power charge message 170, and in turn can identify oneof the equipment profiles 128A-N that matches the WCE identification108, thereby enabling identification of the WCE 102.

From operation 402, the method 400 can proceed to operation 404, whereWPTC 150 and/or the WPT service 124 can determine whether the WCE 102 isassociated with, or otherwise corresponds to an instance of theequipment priority flag 125. For example, if the WCE 102 is an emergencyvehicle or otherwise is considered equipment that should be prioritizedfor wireless power transfer, then the equipment profile corresponding tothe WCE 102 may have or otherwise point to the equipment priority flag125. In some embodiments, if the WPTC 150 and/or WPT service 124determines that the WCE 102 is associated with or otherwise correspondsto an instance of the equipment priority flag 125, then the method 400may proceed along the YES path from operation 404 to operation 406. Forclarity purposes, a discussion of the method 400 proceeding along theYES path to operation 406 will be provided first, followed by adiscussion of the method 400 proceeding along the NO path to operation408.

At operation 406, NED 140 may prepare the OBFT 142 to provide wirelesspower transfer based on the WCE 102 being prioritized for laser-basedwireless power transfer due to the equipment priority flag 125. Forexample, in some embodiments, the NED 140 may prepare the OBFT 142 toprovide wireless power transfer to the WCE 102 upon the WCE 102 enteringthe power transfer range 149 of the NED 140. In some embodiments, whenthe WCE 102 is associated with or otherwise corresponds to an instanceof the equipment priority flag 125, the NED 140 may provide wirelesspower transfer to the WCE 102 irrespective of whether or not the WCE 102has previously been authorized to use the WPT service 124. For example,if the WPTC 150 and/or the WPT service 124 recognizes that the WCE 102is an emergency vehicle, then although the WCE 102 may not have anactive subscription and/or account with a service provider of the WPTservice 124, the NED 140 may still be authorized to provide wirelesspower transfer to the WCE 102. In some embodiments, the NED 140 may beconfigured to provide wireless power transfer only when the WCE 102 hasa current charge level (e.g., the current charge level 107) that isbelow the charge threshold 123. However, in some embodiments, when theWCE 102 is associated with or otherwise corresponds to an instance ofthe equipment priority flag 125, the NED 140 may instruct the OBFT 142to provide wireless power transfer to the WCE 102 irrespective of thecurrent charge level 107 of the WCE 102. In some embodiments, the method400 may proceed from operation 406 to operation 418, discussed below infurther detail.

Returning to operation 404, in some embodiments, if the WPTC 150 and/orthe WPT service 124 determines that the WCE 102 does not correspond withan instance of the equipment priority flag 125, then the method 400 mayproceed along the NO path to operation 408, where the WPTC 150 and/orthe WPT service 124 can determine whether another WCE (e.g., the WCE118) is associated with an instance of the equipment priority flag 125and is requesting wireless power transfer. For example, in an embodimentin which the WCE 118 requests wireless power transfer and correspondswith an instance of the equipment priority flag 125, then WPTC 150and/or the WPT service 124 may attempt to provide wireless powertransfer to the WCE 118 before providing wireless power transfer to theWCE 102. Therefore, in some embodiments, if another WCE (e.g., the WCE118) is associated with the equipment priority flag 125 and isrequesting wireless power transfer, then the method 400 may proceedalong the YES path from operation 408 to operation 410. In someembodiments, if another WCE (e.g., the WCE 118) is not requestingwireless power transfer and/or is not associated with the equipmentpriority flag 125, then the method 400 may proceed along the NO pathfrom operation 408 to operation 414. For clarity purposes, a discussionfollowing the YES path from operation 408 to operation 410 will proceedfirst, followed by a discussion of operation 414.

At operation 410, the WPTC 150 and/or the WPT service 124 may prioritizewireless power transfer to the particular WCE that is associated withthe equipment priority flag 125 (e.g., in an embodiment the WCE 118)such that the WCE 118 is provided wireless power transfer before the WCE102. As such, one or more of the NEDs 140, 160, 164 may provide wirelesspower transfer to the WCE 118 before providing wireless power transferto the WCE 102. From operation 410, the method 400 may proceed tooperation 412, where the WPTC 150 and/or the WPT service 124 maydetermine whether a particular NED (e.g., the NED 140) has completedproviding wireless power transfer to the other WCE (e.g., the WCE 118),such as due to the WCE 118 leaving the power transfer range 149 of theNED 140. In some embodiments, if a particular NED (e.g., the NED 140)has not yet completed providing wireless power transfer, but the NED 140could still provide the WCE 102 with wireless power transfer, then themethod 400 may proceed along the NO path from operation 412 to operation410, where the WPTC 150 and/or the WPT service 124 can continue toprioritize the other WCE (e.g., the WCE 118) for wireless powerdelivery. In some embodiments, if a particular NED (e.g., the NED 140)has completed providing wireless power transfer, and the NED 140 canstill provide the WCE 102 with wireless power transfer, then the method400 may proceed along the YES path from operation 412 to operation 414.

At operation 414, the WPTC 150 and/or the WPT service 124 may determinewhether the current charge level 107 of the WCE 102 is less than thecharge threshold 123. The WPTC 150 and/or the WPT service 124 may beconfigured such that the OBFT 142 will be activated responsive to thecurrent charge level 107 being below the charge threshold 123.Therefore, in some embodiments, if the current charge level 107 is abovethe charge threshold 123, then the method 400 may proceed along the NOpath from operation 414 to operation 416, where the WPTC 150 and/or theWPT service 124 may delay providing wireless power transfer to the WCE102 until the current charge level 107 is indicated to be below thecharge threshold 123. As such, in some embodiments, the method 400 mayproceed from operation 416 to operation 414 where the WPTC 150 and/orthe WPT service 124 can continue to determine whether the current chargelevel 107 is below the charge threshold 123.

Returning to operation 414, in some embodiments, if the WPTC 150 and/orthe WPT service 124 determines that the current charge level 107 isbelow the charge threshold 123, then the method 400 may proceed fromoperation 414 along the YES path to operation 418, where the WPTC 150and/or the WPT service 124 can determine whether the WCE 102 isperforming an operation that is sensitive to charge interruption, suchas indicated by an instance of the charge criticality indicator 110.

In some embodiments, if the WPTC 150 and/or the WPT service 124determines that the WCE 102 is not sensitive to charge interruptions,then the method 400 may proceed along the NO path to operation 420,where the WPTC 150 can prepare the OBFT 142 for wireless power transferto the WCE 102 such that the OBFT 142 can begin providing wireless powertransfer once the WCE 102 enters the power transfer range 149 of the NED140. In some embodiments, the method 400 may proceed from operation 420to one or more operations discussed with respect to method 300illustrated in FIG. 3, such as the operation 310. In some embodiments,the method 400 may proceed from operation 420 to operation 424, wherethe method 400 may end.

Returning to operation 418, in some embodiments, if the WPTC 150 and/orthe WPT service 124 determines that the WCE 102 is sensitive to chargeinterruptions, then the method 400 may proceed along the YES path fromoperation 418 to operation 422, where the WPTC 150 can adjust the OBFT142 to provide additional power transfer to the WCE 102 while the WCE102 is within the power transfer range 149 of the NED 140. For example,the WPTC 150 may decrease a time interval between pulses of wirelesspower transfer (i.e., pulses of the laser beam 143) and thus the OBFT142 is activated more frequently than in a default configuration,thereby enabling additional wireless power transfer to the WCE 102 whilethe WCE 102 is within the power transfer range 149. In some embodiments,the method 400 may proceed from operation 422 to one or more operationsdiscussed with respect to method 300 illustrated in FIG. 3, such as theoperation 310. In some embodiments, the method 400 may proceed fromoperation 422 to operation 424, where the method 400 may end.

Turning now to FIG. 5, a discussion of a network 500 is illustrated,according to an illustrative embodiment. The network 120 and/or the RAN132 shown in FIG. 1 can be configured substantially similar to includeat least some of the elements of the network 500. The network 500 caninclude a cellular network 502, a packet data network 504, for example,the Internet, and a circuit switched network 506, for example, apublicly switched telephone network (“PSTN”). The cellular network 502includes various components such as, but not limited to, basetransceiver stations (“BTSs”), node-B's (“NBs”), e-Node-B's (“eNBs”),g-Node-B's (“gNBs”), base station controllers (“BSCs”), radio networkcontrollers (“RNCs”), mobile switching centers (“MSCs”), mobilemanagement entities (“MMEs”), short message service centers (“SMSCs”),multimedia messaging service centers (“MMSCs”), home location registers(“HLRs”), home subscriber servers (“HSSs”), visitor location registers(“VLRs”), charging platforms, billing platforms, voicemail platforms,GPRS core network components, location service nodes, an IP MultimediaSubsystem (“IMS”), 5G core components, 5G New Radio (“NR”) components,functions, applications, and the like. The cellular network 502 alsoincludes radios and nodes for receiving and transmitting voice, data,and combinations thereof to and from radio transceivers, networks, thepacket data network 504, and the circuit switched network 506.

A mobile communications device 508, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 502. The cellular network502 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 502 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSUPA), and HSPA+. The cellular network502 also can be compatible with, and/or otherwise configured toimplement and support, mobile communications standards such as but notlimited to 4G, LTE, LTE Advanced, and/or 5G NR, as well as evolved andfuture mobile standards.

The packet data network 504 includes various devices, for example,servers, computers, databases, and other devices in communication withone another, as is generally understood. The packet data network 504devices are accessible via one or more network links. The servers oftenstore various files that are provided to a requesting device such as,for example, a computer, a terminal, a smartphone, or the like.Typically, the requesting device includes software (a “browser”) forexecuting a web page in a format readable by the browser or othersoftware. Other files and/or data may be accessible via “links” and/or“pointers” in the retrieved files, as is generally understood. In someembodiments, the packet data network 504 includes or is in communicationwith the Internet. The circuit switched network 506 includes varioushardware and software for providing circuit switched communications. Thecircuit switched network 506 may include, or may be, what is oftenreferred to as a plain old telephone system (POTS). The functionality ofa circuit switched network 506 or other circuit-switched network aregenerally known and will not be described herein in detail.

The illustrated cellular network 502 is shown in communication with thepacket data network 504 and a circuit switched network 506, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 510, for example, a PC, a laptop, a portabledevice, or another suitable device, can communicate with one or morecellular networks 502, and devices connected thereto, through the packetdata network 504. It also should be appreciated that theInternet-capable device 510 can communicate with the packet data network504 through the circuit switched network 506, the cellular network 502,and/or via other networks (not illustrated).

As illustrated, a communications device 512, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 506, and therethrough to the packetdata network 504 and/or the cellular network 502. It should beappreciated that the communications device 512 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 510. In some embodiments, the mobilecommunications device 508, the Internet-capable device 510, and/or thecommunication device 512 can correspond with one or more computersystems, devices, and/or equipment discussed with respect to FIG. 1,such as but not limited to the WCE 102, the WCE 118, the network server122, the NED 140, the NED 160, and/or the NED 164. In the specification,the network 120, the RAN 132, and/or the network 500 can refer broadlyto, in some embodiments, any combination of the networks 502, 504, 506.It should be appreciated that substantially all of the functionalitydescribed with reference to the network 120, the RAN 132, and/or thenetwork 500 can, in some embodiments, be performed by the cellularnetwork 502, the packet data network 504, and/or the circuit switchednetwork 506, alone or in combination with other networks, networkelements, and the like.

FIG. 6 is a block diagram illustrating a computer system 600 can beconfigured to provide the functionality described herein related towireless power transfer network management, in accordance with variousembodiments of the concepts and technologies disclosed herein. In someembodiments, at least a portion of one or more of the WCE 102, the WCE118, the network server 122, the NED 140, the NED 160, and/or the NED164 illustrated and described herein can be configured as and/or canhave an architecture similar or identical to the computer system 600.The computer system 600 includes a processing unit 602, a memory 604,one or more user interface devices 606, one or more input/output (“I/O”)devices 608, and one or more network devices 610, each of which isoperatively connected to a system bus 612. The system bus 612 enablesbi-directional communication between the processing unit 602, the memory604, the user interface devices 606, the I/O devices 608, and thenetwork communication devices 610. In some embodiments, the vehicleprocessor 203 can be configured as, or at least similar to, an instanceof the processing unit 602. In some embodiments, one or more instancesof the processing unit 602 can be implemented within one or more devicesand/or components of the operating environment 100, such as but notlimited to one or more of the WCE 102, the WCE 118, the network server122, the NED 140, the NED 160, and/or the NED 164. In some embodiments,the vehicle memory 204 can be configured substantially similar to thememory 604. In some embodiments, one or more instances of the memory 604can be implemented within one or more devices and/or components of theoperating environment 100, such as but not limited to one or more of theWCE 102, the WCE 118, the network server 122, the NED 140, the NED 160,and/or the NED 164. In various embodiments, one or more aspects of theNED 140 and/or the WCE 102 can be included within the computer system600.

The processing unit 602 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. As used herein,the word “processor” and/or the phrase “processing unit” when used withregard to any architecture or system can include multiple processors orprocessing units distributed across and/or operating in sequence and/orparallel in a single machine or in multiple machines. Furthermore,processors and/or processing units can be used to support virtualprocessing environments. Processors and processing units also caninclude state machines, application-specific integrated circuits(“ASICs”), combinations thereof, or the like. As used herein, the phrase“processing unit” may be referred to as a “processor.” The processingunit 602 can include one or more central processing units (“CPUs”)configured with one or more processing cores. The processing unit 602can include one or more graphics processing unit (“GPU”) configured toaccelerate operations performed by one or more CPUs, and/or to performcomputations to process data, and/or to execute computer-executableinstructions of one or more application programs, operating systems,and/or other software that may or may not include instructionsparticular to graphics computations. In some embodiments, the processingunit 602 can include one or more discrete GPUs. In some otherembodiments, the processing unit 602 can include CPU and GPU componentsthat are configured in accordance with a co-processing CPU/GPU computingmodel, wherein the sequential part of an application executes on the CPUand the computationally-intensive part is accelerated by the GPU. Theprocessing unit 602 can include one or more system-on-chip (“SoC”)components along with one or more other components including, forexample, a memory, a communication component, or some combinationthereof. In various embodiments, an instance of a processor (e.g., theprocessing unit 602) can be and/or can include one or more SNAPDRAGONSoCs, a cellular V2X (“C-V2X”) chipset, and/or another architectureavailable from QUALCOMM of San Diego, Calif.; one or more TEGRA SoCsand/or another architecture available from NVIDIA of Santa Clara,Calif.; one or more HUMMINGBIRD SoCs and/or another architectureavailable from SAMSUNG of Seoul, South Korea; one or more OpenMultimedia Application Platform (“OMAP”) SoCs and/or anotherarchitecture available from TEXAS INSTRUMENTS of Dallas, Tex.; one ormore customized versions of any of the above SoCs; and/or one or moreproprietary SoCs and/or proprietary circuitry capable of supporting V2Xcommunication processing. In various embodiments, an instance of aprocessor (e.g., the processing unit 602) can be and/or can include oneor more hardware components architected in accordance with an ARMarchitecture, available for license from ARM HOLDINGS of Cambridge,United Kingdom. Alternatively (or additionally), an instance of aprocessor (e.g., the processing unit 602) can be or can include one ormore hardware components architected in accordance with an x86architecture, such as an architecture available from INTEL CORPORATIONof Mountain View, Calif., and others. Those skilled in the technologywill appreciate that the implementation of a processor (e.g., theprocessing unit 602) can utilize various computation architectures, andas such, a processor (e.g., the processing unit 602) should not beconstrued as being limited to any particular computation architecture orcombination of computation architectures, including those explicitlydisclosed herein. Because processors and/or processing units aregenerally known to one of ordinary skill, the processors and processingunits disclosed and discussed herein will not be described in furtherdetail herein.

The memory 604 communicates with the processing unit 602 via the systembus 612. In some embodiments, the memory 604 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 602 via the system bus 612. The memory 604 includes anoperating system 614 and one or more program modules 616. The operatingsystem 614 can include, but is not limited to, members of the WINDOWS,WINDOWS CE, and/or WINDOWS MOBILE families of operating systems fromMICROSOFT CORPORATION, the LINUX family of operating systems, theSYMBIAN family of operating systems from SYMBIAN LIMITED, the BREWfamily of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS,and/or LEOPARD families of operating systems from APPLE CORPORATION, theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems, and the like.

The program modules 616 may include various software, program modules,or other computer readable and/or executable instructions that configurehardware resources of the computer system 600, such as but not limitedto the processing unit 602 described herein. In some embodiments, forexample, the program modules 616 can include the WPTC 150, the WPTservice 124, and/or other computer-readable instructions. These and/orother programs can be embodied in computer-executable instructions that,when executed by the processing unit 602, can facilitate performance ofone or more of the methods 300 and/or 400 described in detail above withrespect to FIGS. 3 and 4. According to some embodiments, the programmodules 616 may be embodied in hardware, software, firmware, or anycombination thereof. It should be understood that the memory 604 alsocan be configured to store one or more instance of information and datadiscussed with respect to FIGS. 1, 2, 3, and 4, such as but not limitedto the charge threshold 123, the power authorization map 126, theauthorized identifiers 127A-N, the equipment profiles 128A-N, the NEDlocation identifiers 129A-N, the equipment priority flag 125, the powercharge message 170, the current charge profile 172, the adjustmentinstruction 174, the charge preparation command 180, the chargepreparation command 182, and/or other data, if desired.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 600. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the computer system 600. In the claims, the phrases“memory,” “computer storage medium” and variations thereof does notinclude waves or signals per se and/or communication media.

The user interface devices 606 may include one or more devices withwhich a user accesses the computer system 600. The user interfacedevices 606 may include, but are not limited to, computers, servers,personal digital assistants, cellular phones, or any suitable computingdevices that can communicate with the computer system 600. The I/Odevices 608 enable a user to interface with the program modules 616. Inone embodiment, the I/O devices 608 are operatively connected to an I/Ocontroller (not shown) that enables communication with the processingunit 602 via the system bus 612. The I/O devices 608 may include one ormore input devices, such as, but not limited to, a keyboard, a mouse, oran electronic stylus. Further, the I/O devices 608 may include one ormore output devices, such as, but not limited to, a display screen or aprinter.

The network communication devices 610 enable the computer system 600 tocommunicate with other networks or remote systems via a network, such asnetwork 618. Examples of network communication devices 610 include, butare not limited to, a modem, a radio frequency (“RF”) transceiver and/orinfrared (“IR”) transceiver, a telephonic interface, a bridge, a router,or a network card. The network 618 may include a wireless network suchas, but not limited to, a Wireless Local Area Network (“WLAN”) such as aWI-FI network, a Wireless Wide Area Network (“WWAN”), a WirelessPersonal Area Network (“WPAN”) such as BLUETOOTH, a WirelessMetropolitan Area Network (“WMAN”) such a WiMAX network, or a cellularnetwork. Alternatively, the network 618 may be a wired network such as,but not limited to, a Wide Area Network (“WAN”) such as the Internet, aLocal Area Network (“LAN”) such as the Ethernet, a wired Personal AreaNetwork (“PAN”), or a wired Metropolitan Area Network (“MAN”). In someembodiments, the network 618 may include one or more aspects of thenetwork 500, discussed above. It should be understood that the examplesprovided are for illustration purposes only, and therefore should not beconstrued as limiting in any way.

Turning now to FIG. 7, an illustrative user equipment 700 and componentsthereof will be described. In some embodiments, the WCE 102, the WCE 118and/or other devices illustrated and described herein can be configuredas and/or can have an architecture similar or identical to the userequipment 700 described herein in FIG. 7. It should be understood,however, that the various devices illustrated and described herein mayor may not include the functionality described herein with reference toFIG. 7. While connections are not shown between the various componentsillustrated in FIG. 7, it should be understood that some, none, or allof the components illustrated in FIG. 7 can be configured to interactwith one other to carry out various device functions. In someembodiments, the components are arranged so as to communicate via one ormore busses (not shown). In various embodiments, aspects from one ormore the WCE 102 and/or the vehicle 201 can be configured or otherwiseimplemented in the user equipment 700. As such, an instance ofwirelessly chargeable equipment (e.g., the WCE 102) and/or the vehicle201 may include one or more aspects of the user equipment 700 discussedherein. Thus, it should be understood that FIG. 7 and the followingdescription are intended to provide a general understanding of asuitable environment in which various aspects of embodiments can beimplemented, and should not be construed as being limiting in any way.

As illustrated in FIG. 7, the user equipment 700 can include a display702 for presenting data and information. According to variousembodiments, the display 702 can be configured to present variousgraphical user interface (“GUI”) elements for presenting and/ormodifying information associated with audiovisual content, anaudiovisual content filter, presenting text, images, video, virtualkeypads and/or keyboards, messaging data, notification messages,metadata, internet content, device status, time, date, calendar data,device preferences, map and location data, combinations thereof, and/orthe like. The user equipment 700 also can include a processor 704 and amemory or other data storage device (“memory”) 706. The processor 704can be configured to process data and/or can execute computer-executableinstructions stored in the memory 706. The computer-executableinstructions executed by the processor 704 can include, for example, anoperating system 708, one or more applications 710 such as a displayapplication that can present various communications, messages, and/orother computer-executable instructions stored in a memory 706, or thelike. In some embodiments, the applications 710 also can include a UIapplication (not illustrated in FIG. 7) and/or vehicle softwareapplications, such as discussed with respect to FIG. 2.

The UI application can interface with the operating system 708 tofacilitate any of the operations discussed herein and functionality forpresenting content and/or data stored at and/or received by the userequipment 700 and/or stored elsewhere. It is understood that one or moreinstances of the operating system 708 may be included and operate withinone or more systems discussed with respect to the operating environment100, such as but not limited to the WCE 102 and/or the WCE 118. In someembodiments, the operating system 708 can include a member of theSYMBIAN OS family of operating systems from SYMBIAN LIMITED, a member ofthe WINDOWS MOBILE OS and/or WINDOWS PHONE OS families of operatingsystems from MICROSOFT CORPORATION, a member of the PALM WEBOS family ofoperating systems from HEWLETT PACKARD CORPORATION, a member of theBLACKBERRY OS family of operating systems from RESEARCH IN MOTIONLIMITED, a member of the IOS family of operating systems from APPLEINC., a member of the ANDROID OS family of operating systems from GOOGLEINC., and/or other operating systems. These operating systems are merelyillustrative of some contemplated operating systems that may be used inaccordance with various embodiments of the concepts and technologiesdescribed herein and therefore should not be construed as being limitingin any way.

The UI application can be executed by the processor 704 to aid a user inpresenting content, interacting with the NED 140, engaging with the WPTservice 124, presenting a vehicle communication, providing feedback orother information about the user equipment 700, presenting a conditionidentifier, configuring settings, manipulating address book contentand/or settings, multimode interaction, interacting with otherapplications 710, and otherwise facilitating user interaction with theoperating system 708, the applications 710, and/or other types orinstances of data 712 that can be stored at the user equipment 700, suchas stored by the memory 706. According to various embodiments, the data712 can include, for example, instances of the current charge level 107,the WCE identifier 108, the location identifier 109, the chargecriticality indicator 110, any other elements discussed with respect toFIGS. 1, 2, 3, and 4, presence applications, wireless power transferinformation, visual voice mail applications, messaging applications,text-to-speech and speech-to-text applications, add-ons, plug-ins, emailapplications, music applications, video applications, cameraapplications, location-based service applications, power conservationapplications, game applications, productivity applications,entertainment applications, enterprise applications, combinationsthereof, and the like. The applications 710, the data 712, and/orportions thereof can be stored in the memory 706 and/or in a firmware714, and can be executed by the processor 704. The firmware 714 also canstore code for execution during device power up and power downoperations. It can be appreciated that the firmware 714 can be stored ina volatile or non-volatile data storage device including, but notlimited to, the memory 706 and/or a portion thereof.

The user equipment 700 also can include an input/output (“I/O”)interface 716. One or more instances of the I/O interface 716 can beincluded any system and/or device discussed in FIG. 1 (e.g., the WCE102). The I/O interface 716 can be configured to support theinput/output of data such as a message, communication, command, and/orinstruction, and/or any other information or elements discussed withrespect to FIGS. 1, 2, 3, and 4, user information, organizationinformation, presence status information, user IDs, passwords, andapplication initiation (start-up) requests. In some embodiments, the I/Ointerface 716 can include a hardwire connection such as a universalserial bus (“USB”) port, a mini-USB port, a micro-USB port, an audiojack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, aparallel port, an Ethernet (RJ45) port, an RJ11 port, a proprietaryport, combinations thereof, or the like. In some embodiments, the userequipment 700 can be configured to synchronize with another device totransfer content to and/or from the user equipment 700. In someembodiments, the user equipment 700 can be configured to receive updatesto one or more of the applications 710 via the I/O interface 716, thoughthis is not necessarily the case. In some embodiments, the I/O interface716 accepts I/O devices such as keyboards, keypads, mice, interfacetethers, printers, plotters, external storage, touch/multi-touchscreens, touch pads, trackballs, joysticks, microphones, remote controldevices, displays, projectors, medical equipment (e.g., stethoscopes,heart monitors, and other health metric monitors), modems, routers,external power sources, docking stations, combinations thereof, and thelike. It should be appreciated that the I/O interface 716 may be usedfor communications between the user equipment 700 and a network deviceor local device.

The user equipment 700 also can include a communications component 718.The communications component 718 can be configured to interface with theprocessor 704 to facilitate wired and/or wireless communications withone or more networks (e.g., the network 120 and/or the RAN 132) and/or anetwork edge device (e.g., the NEDs 140, 160, 164) described herein. Insome embodiments, other networks include networks that utilizenon-cellular wireless technologies such as WI-FI or WIMAX. In someembodiments, the communications component 718 includes a multimodecommunications subsystem for facilitating communications via thecellular network and one or more other networks. The communicationscomponent 718, in some embodiments, includes one or more transceivers.The one or more transceivers, if included, can be configured tocommunicate over the same and/or different wireless technology standardswith respect to one another. For example, in some embodiments one ormore of the transceivers of the communications component 718 may beconfigured to communicate using GSM, CDMAONE, CDMA2000, LTE, and variousother 2G, 2.5G, 3G, 4G, LTE, LTE Advanced, 5G New Radio, and greatergeneration technology standards. Moreover, the communications component718 may facilitate communications over various channel access methods(which may or may not be used by the aforementioned standards)including, but not limited to, TDMA, FDMA, W-CDMA, OFDMA, SDMA, and thelike.

In addition, the communications component 718 may facilitate datacommunications using GPRS, EDGE, the HSPA protocol family includingHSDPA, EUL or otherwise termed HSUPA, HSPA+, and various other currentand future wireless data access standards. In the illustratedembodiment, the communications component 718 can include a firsttransceiver (“TxRx”) 720A that can operate in a first communicationsmode (e.g., GSM). The communications component 718 also can include anN^(th) transceiver (“TxRx”) 720N that can operate in a secondcommunications mode relative to the first transceiver 720A (e.g., UMTS).While two transceivers 720A-N (hereinafter collectively and/orgenerically referred to as “transceivers 720”) are shown in FIG. 7, itshould be appreciated that less than two, two, and/or more than twotransceivers 720 can be included in the communications component 718.

The communications component 718 also can include an alternativetransceiver (“Alt TxRx”) 722 for supporting other types and/or standardsof communications. According to various contemplated embodiments, thealternative transceiver 722 can communicate using various communicationstechnologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared,infrared data association (“IRDA”), near field communications (“NFC”),other RF technologies, combinations thereof, and the like. In someembodiments, the communications component 718 also can facilitatereception from terrestrial radio networks, digital satellite radionetworks, internet-based radio service networks, combinations thereof,and the like. The communications component 718 can process data from anetwork such as the Internet, an intranet, a broadband network, a WI-FIhotspot, an Internet service provider (“ISP”), a digital subscriber line(“DSL”) provider, a broadband provider, combinations thereof, or thelike. In some embodiments, the communications component 718 can supportone or more communication modes discussed with respect to FIG. 2, suchas the direct transmission mode 219 over a PC5 interface and/or thenetwork transmission mode 221 over a Uu interface.

The user equipment 700 also can include one or more sensors 724. Thesensors 724 can include temperature sensors, light sensors, air qualitysensors, movement sensors, orientation sensors, noise sensors, proximitysensors, or the like. As such, it should be understood that the sensors724 can include, but are not limited to, accelerometers, magnetometers,gyroscopes, infrared sensors, noise sensors, radars, microphones,combinations thereof, or the like. Additionally, audio capabilities forthe user equipment 700 may be provided by an audio I/O component 726.The audio I/O component 726 of the user equipment 700 can include one ormore speakers for the output of audio signals, one or more microphonesfor the collection and/or input of audio signals, and/or other audioinput and/or output devices. In some embodiments, the audio I/Ocomponent 726 maybe included as a component of the display 702. Forexample, in some embodiments, the display 702 can provide and presentvisual images and/or audio input and/or audio output. In someembodiments, the I/O interface 716 can include direct communicativecoupling with the display 702 and/or the audio I/O component 726 so asto provide transfer and input and/or output of visual images (e.g., fromthe display 702) and/or audio clips (e.g., from the audio I/O component726) to and/or from the user equipment 700.

The illustrated user equipment 700 also can include a subscriberidentity module (“SIM”) system 728. The SIM system 728 can include auniversal SIM (“USIM”), a universal integrated circuit card (“UICC”)and/or other identity devices. The SIM system 728 can include and/or canbe connected to or inserted into an interface such as a slot interface730. In some embodiments, the slot interface 730 can be configured toaccept insertion of other identity cards or modules for accessingvarious types of networks. Additionally, or alternatively, the slotinterface 730 can be configured to accept multiple subscriber identitycards. Because other devices and/or modules for identifying users and/orthe user equipment 700 are contemplated, it should be understood thatthese embodiments are illustrative, and should not be construed as beinglimiting in any way.

The user equipment 700 also can include an image capture and processingsystem 732 (“image system”). The image system 732 can be configured tocapture or otherwise obtain photos, videos, and/or other visualinformation. As such, the image system 732 can include cameras, lenses,charge-coupled devices (“CCDs”), combinations thereof, or the like. Theuser equipment 700 may also include a video system 734. The video system734 can be configured to capture, process, record, modify, and/or storevideo content. Photos and videos obtained using the image system 732 andthe video system 734, respectively, may be added as message content toan MMS message, email message, and sent to another user equipment. Thevideo and/or photo content also can be shared with other devices viavarious types of data transfers via wired and/or wireless user equipmentas described herein.

The user equipment 700 also can include one or more location components736. The location components 736 can be configured to send and/orreceive signals to determine a geographic location of the user equipment700. According to various embodiments, the location components 736 cansend and/or receive signals from global positioning system (“GPS”)devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellularnetwork triangulation data, combinations thereof, and the like. Thelocation component 736 also can be configured to communicate with thecommunications component 718 to retrieve triangulation data fordetermining a location of the user equipment 700. In some embodiments,the location component 736 can interface with cellular network nodes,telephone lines, satellites, location transmitters and/or beacons,wireless network transmitters and receivers, combinations thereof, andthe like. In some embodiments, the location component 736 can includeand/or can communicate with one or more of the sensors 724 such as acompass, an accelerometer, and/or a gyroscope to determine theorientation of the user equipment 700. Using the location component 736,the user equipment 700 can generate and/or receive data to identify itsgeographic location, or to transmit data used by other devices todetermine the location of the user equipment 700. The location component736 may include multiple components for determining the location and/ororientation of the user equipment 700.

The illustrated user equipment 700 also can include a power source 738.The power source 738 can include one or more batteries, power supplies,power cells, and/or other power subsystems including alternating current(“AC”) and/or direct current (“DC”) power devices. The power source 738also can interface with an external power system or charging equipmentvia a power I/O component 740. Because the user equipment 700 caninclude additional and/or alternative components, the above embodimentshould be understood as being illustrative of one possible operatingenvironment for various embodiments of the concepts and technologiesdescribed herein. The described embodiment of the user equipment 700 isillustrative, and therefore should not be construed as being limiting inany way.

Based on the foregoing, it should be appreciated that concepts andtechnologies directed to wireless power transfer network management havebeen disclosed herein. Although the subject matter presented herein hasbeen described in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer-readable mediums, it is to be understood that the conceptsand technologies disclosed herein are not necessarily limited to thespecific features, acts, or mediums described herein. Rather, thespecific features, acts and mediums are disclosed as example forms ofimplementing the concepts and technologies disclosed herein.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments of the concepts and technologies disclosed herein.

What is claimed is:
 1. A system comprising: an optical beamformingtransmitter; a processor; and a memory that stores computer-executableinstructions that, in response to execution by the processor, cause theprocessor to perform operations comprising: receiving a power chargemessage that requests wireless power transfer to charge a battery systemof a wirelessly chargeable equipment, detecting that the wirelesslychargeable equipment is within a power transfer range of the opticalbeamforming transmitter, determining that the wirelessly chargeableequipment is not stationary, tracking movement of the wirelesslychargeable equipment, determining a charge criticality indicatorassociated with the wirelessly chargeable equipment, and activating,based at least in part on the charge criticality indicator associatedwith the wirelessly chargeable equipment, the optical beamformingtransmitter that provides wireless power transfer via a laser beam tothe wirelessly chargeable equipment while the wirelessly chargeableequipment is within the power transfer range, wherein activating theoptical beamforming transmitter comprises adjusting a time intervalbetween pulses of the laser beam based at least in part on the chargecriticality indicator associated with the wirelessly chargeableequipment.
 2. The system of claim 1, wherein the power charge messagecomprises a wirelessly chargeable equipment identifier and a locationidentifier.
 3. The system of claim 1, wherein the operations furthercomprise obtaining a current charge profile corresponding to thewirelessly chargeable equipment.
 4. The system of claim 3, wherein thecurrent charge profile includes the charge criticality indicator and acurrent charge level.
 5. The system of claim 1, wherein the operationsfurther comprise determining whether the wirelessly chargeable equipmentis authorized to receive the wireless power transfer.
 6. The system ofclaim 1, wherein the operations further comprise: prior to thewirelessly chargeable equipment leaving the power transfer range,generating a charge preparation command that is directed to a downstreamwireless power transfer assembly that is located outside of the powertransfer range; and providing the charge preparation command to thedownstream wireless power transfer assembly that is located outside ofthe power transfer range.
 7. The system of claim 6, wherein the chargepreparation command instructs the downstream wireless power transferassembly to prepare to provide wireless power transfer for thewirelessly chargeable equipment.
 8. The system of claim 1, wherein theoptical beamforming transmitter is activated responsive to confirming adirect line of sight with the wirelessly chargeable equipment.
 9. Amethod comprising: receiving, by a system that provides an opticalbeamforming transmitter, a power charge message that requests wirelesspower transfer to charge a battery system of a wirelessly chargeableequipment; detecting, by the system, that the wirelessly chargeableequipment is within a power transfer range of the optical beamformingtransmitter; determining, by the system, that the wirelessly chargeableequipment is not stationary; tracking, by the system, movement of thewirelessly chargeable equipment; determining a charge criticalityindicator associated with the wirelessly chargeable equipment; andactivating, by the system based at least in part on the chargecriticality indicator associated with the wirelessly chargeableequipment, the optical beamforming transmitter that provides wirelesspower transfer via a laser beam to the wirelessly chargeable equipmentwhile the wirelessly chargeable equipment is within the power transferrange, wherein activating the optical beamforming transmitter comprisesadjusting a time interval between pulses of the laser beam based atleast in part on the charge criticality indicator associated with thewirelessly chargeable equipment.
 10. The method of claim 9, furthercomprising obtaining a current charge profile corresponding to thewirelessly chargeable equipment.
 11. The method of claim 10, wherein thecurrent charge profile includes the charge criticality indicator and acurrent charge level.
 12. The method of claim 9, further comprisingdetermining, by the system, whether the wirelessly chargeable equipmentis authorized to receive the wireless power transfer.
 13. The method ofclaim 9, further comprising: prior to the wirelessly chargeableequipment leaving the power transfer range, generating, by the system, acharge preparation command that is directed to a downstream wirelesspower transfer assembly that is located outside of the power transferrange; and providing, from the system, the charge preparation command tothe downstream wireless power transfer assembly that is located outsideof the power transfer range.
 14. The method of claim 13, wherein thecharge preparation command instructs the downstream wireless powertransfer assembly to prepare to provide wireless power transfer for thewirelessly chargeable equipment.
 15. The method of claim 9, wherein theoptical beamforming transmitter is activated responsive to confirming adirect line of sight with the wirelessly chargeable equipment.
 16. Acomputer storage medium having computer-executable instructions storedthereon that, in response to execution by a processor of a systemcomprising an optical beamforming transmitter, causes the processor toperform operations comprising: receiving a power charge message thatrequests wireless power transfer to charge a battery system of awirelessly chargeable equipment; detecting that the wirelesslychargeable equipment is within a power transfer range of the opticalbeamforming transmitter; determining that the wirelessly chargeableequipment is not stationary; tracking movement of the wirelesslychargeable equipment; determining a charge criticality indicatorassociated with the wirelessly chargeable equipment; and activating,based at least in part on the charge criticality indicator associatedwith the wirelessly chargeable equipment, the optical beamformingtransmitter that provides wireless power transfer via a laser beam tothe wirelessly chargeable equipment while the wirelessly chargeableequipment is within the power transfer range, wherein activating theoptical beamforming transmitter comprises adjusting a time intervalbetween pulses of the laser beam based at least in part on the chargecriticality indicator associated with the wirelessly chargeableequipment.
 17. The computer storage medium of claim 16, wherein theoperations further comprise obtaining a current charge profilecorresponding to the wirelessly chargeable equipment.
 18. The computerstorage medium of claim 16, wherein the operations further comprisedetermining whether the wirelessly chargeable equipment is authorized toreceive the wireless power transfer.
 19. The computer storage medium ofclaim 16, wherein the operations further comprise: prior to thewirelessly chargeable equipment leaving the power transfer range,generating a charge preparation command that is directed to a downstreamwireless power transfer assembly that is located outside of the powertransfer range; and providing the charge preparation command to thedownstream wireless power transfer assembly that is located outside ofthe power transfer range.
 20. The computer storage medium of claim 16,wherein the optical beamforming transmitter is activated responsive toconfirming a direct line of sight with the wirelessly chargeableequipment.